[ https://issues.jboss.org/browse/JBESB-3844?page=com.atlassian.jira.plugin... ] Sato Tadayoshi updated JBESB-3844: ---------------------------------- Comment: was deleted (was: The original issue from which this issue spun off.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBESB-3844?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated JBESB-3844: ------------------------------------------- Bugzilla Update: Perform -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBESB-3844?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3844: ------------------------------------------------ Tadayoshi Sato <tasato(a)redhat.com&gt; made a comment on [bug 856600|https://bugzilla.redhat.com/show_bug.cgi?id=856600] 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=MyCategor... 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=MyCategor... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira