[
https://jira.jboss.org/jira/browse/JBESB-2465?page=com.atlassian.jira.plu...
]
Gerbrand de Goeij updated JBESB-2465:
-------------------------------------
Attachment: patch_HttpProtocol.txt
To solve this issue I've introduced a new paramter called "protocol-socket"
which specifies the socket protocol. Otherwise the WSDL should be parsed to check the
endpoint socket protocol.
This patch is for the
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_5_GA
branch.
HttpProtocol class should check SOAP endpoint address in stead of
target-host-url property
------------------------------------------------------------------------------------------
Key: JBESB-2465
URL:
https://jira.jboss.org/jira/browse/JBESB-2465
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.5
Reporter: Gerbrand de Goeij
Attachments: patch_HttpProtocol.txt
In the org.jboss.soa.esb.http.configurators.HttpProtocol class, in the method configure
there is a check if the scheme of the targetURI starts with "http".
But when you want to use a WSDL that is located on the file system (ie. because the WSDL
is not available online) this piece of code does not work (because in my case the
targetURI (property "target-host-url") starts with "file://...".
Therefore I think it's better to base the decision on which ProtocolSocketFactory
should be used upon the SOAP endpoint address (in stead of the WSDL location URI).
--
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