[
https://jira.jboss.org/jira/browse/JBESB-1936?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBESB-1936:
-------------------------------------
After talking to Kev... what we're going to implement for this (for now anyway) is
simply exposing the WSDL's of the SOAPClient actions. It will be up to the pipeline
to to transform the incoming SOAP into the appropriate Java Object Graph before passing it
to the SOAPClient action.
Of source, the pipeline isn't going to receive the SOAP request until after JBESB-2334
is done. Without JBESB-2334, the SOAP client will see the actual WS endpoint.
Create a contract publisher to handle remote WS endpoints
---------------------------------------------------------
Key: JBESB-1936
URL:
https://jira.jboss.org/jira/browse/JBESB-1936
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.4
Reporter: Kevin Conner
Assignee: Tom Fennelly
Fix For: 4.5
We have a contract publisher that exposes wsdl for a co-located JBoss WS endpoint,
WebserviceContractPublisher. We should have an equivalent that can be used to expose the
wsdl of remote services through the ESB.
--
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