[
https://jira.jboss.org/jira/browse/JBESB-2855?page=com.atlassian.jira.plu...
]
David Ward updated JBESB-2855:
------------------------------
Description:
When configuring the SOAPProxy action with a wsdl, only http:// (and https://) urls are
handled (and it can handle Basic Auth).
Additional urns schemas supported should be:
1. file:// for local wsdl files
2. classpath:// for wsdl files found on the classpath
3. internal:// for wsdl provided by the local JBoss Web Services
was:
When configuring the SOAPProxy action with a wsdl, only http:// (and https://) urls are
handled (and it can handle Basic Auth).
Additional urns schemas supported should be:
1. file:// for local wsdl files
2. classpath:// for wsdl files found on the classpath
3. local:// (or internal:// ?) for wsdl provided by the local JBoss Web Services
#3 is important so that when the SOAPProxy is proxying to a web service that is deployed
in the same JVM, and Tomcat is not yet accepting requests such that the SOAPProxy
can't yet pull the local wsdl via http, that JBoss WS is queried locally so nothing
breaks.
SOAPProxy to handle non-http URLs for wsdl location
---------------------------------------------------
Key: JBESB-2855
URL:
https://jira.jboss.org/jira/browse/JBESB-2855
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.6
Reporter: David Ward
Assignee: David Ward
Fix For: 4.7
When configuring the SOAPProxy action with a wsdl, only http:// (and https://) urls are
handled (and it can handle Basic Auth).
Additional urns schemas supported should be:
1. file:// for local wsdl files
2. classpath:// for wsdl files found on the classpath
3. internal:// for wsdl provided by the local JBoss Web Services
--
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