WSDL/schema import locations improperly rewritten by HttpSOAPProxyWsdlLoader in contract
application when using JBRGateway+HTTP
-------------------------------------------------------------------------------------------------------------------------------
Key: JBESB-3161
URL:
https://jira.jboss.org/jira/browse/JBESB-3161
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: David Ward
Assignee: David Ward
Fix For: 4.7 CP1
The only two endpoints we expose contract information for via the contract JSP application
are both HTTP protocol based: one using the new HTTPGateway, and one using the
JBossRemotingGateway/HTTP. JBESB-3076 fixed an issue where the imports within the WSDL or
XSD were not working properly. However, whereas many different import scenarios were
tested (see that jira's comments), all testing was done using the HTTPGateway. Upon
further testing, it was discovered that the WSDL/schema import locations are being
improperly rewritten *when* using the JBossRemotingGateway/HTTP instead.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira