Description of problem: Platform BZ for https://issues.jboss.org/browse/JBESB-3844 Turning 'cache-schemas' introduced by JBESB-3802 to true doens't rewrite the schema imports in WSDLs correctly for the JBoss Remoting Gateway. The definitions/import/@location or the definitions/types/schema/import/@schemaLocation in a WSDL should be rewritten to: http://localhost:8080/contract/contract.jsp?wsdl&serviceCat=MyCategory&serviceName=MyService&protocol=http&resource=hello.xsd but actually: http://localhost:8765/?wsdl&resource=hello.xsd where the JBR gateway is configured at http://localhost:8765. How reproducible: Easy Steps to Reproduce: 1. Make a contract-first web service whose WSDL contains XSD imports and deploy it to SOA-P. 2. Make an ESB service which proxies the above web service using SOAPProcessor or SOAPProxy and re-publishes it through JBR Gateway/HTTP and deploy it to SOA-P. 3. Check the proxied WSDL from the contract web. Actual results: The schemaLocation attribute of an imported XSD looks like: http://localhost:8765/?wsdl&resource=hello.xsd Expected results: The schemaLocation attribute should be like: http://localhost:8080/contract/contract.jsp?wsdl&serviceCat=MyCategory&serviceName=MyService&protocol=http&resource=hello.xsd