[
https://issues.jboss.org/browse/JBESB-3802?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3802:
------------------------------------------------
Jason Shepherd <jshepherd(a)redhat.com> made a comment on [bug
823711|https://bugzilla.redhat.com/show_bug.cgi?id=823711]
I've attached a reproducer for this issue.
Please run it like this:
1. Unzip the contract_wsdl_include to the $SOA_HOME/samples/quickstarts directory.
2. Start SOA-P
3. Deploy the quickstart by running 'ant deploy'
4. Observe the WSDL published at
http://127.0.0.1:8080/Quickstart_contract_wsdl_include/http/MyServiceCate...
Expected Result:
The XSD imported by the WSDL should be available under the same context as the wsdl. eg:
<xsd:schema>
<xsd:import namespace="http://webservice_producer/helloworld"
schemaLocation="Quickstart_contract_wsdl_include/http/MyServiceCategory/MyWSProducerService?wsdl&resource=HelloWorldService.xsd"/>
</xsd:schema>
Actual Result:
<xsd:schema>
<xsd:import namespace="http://webservice_producer/helloworld"
schemaLocation="http://127.0.0.1:8080/Quickstart_HelloWorldWS/HelloWorldWS?wsdl&resource=HelloWorldService.xsd"/>
</xsd:schema>
Rewrite schemas imported by SOAPProcessor to point to locally cached
versions
-----------------------------------------------------------------------------
Key: JBESB-3802
URL:
https://issues.jboss.org/browse/JBESB-3802
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Environment: JBoss Enterprise SOA-P 5.2
Reporter: Jason Shepherd
When wrapping an external webservice using SOAPProcessor, the contract is correctly
published in the contract web application, see JBESB-3789. However any schema files
imported by the wrapped web service are referenced on the wrapped web service, they are
not cached by the ESB. Please cache a copy of the imported schemas locally, so that a
client of the ESB does not have to contact the original, wrapped, web service to retrieve
the schemas.
This issue will fix will also effect JBR, HTTP gateway schemas as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira