[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3789:
------------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
817747|https://bugzilla.redhat.com/show_bug.cgi?id=817747]
Sato Tadayoshi <tasato(a)redhat.com> made a comment on jira JBESB-3789
Thanks Magesh for quick fixing. But unfortunatelly I tested the fix and found it's not
complete.
Explaining based on the reproducing step above, the WSDL contract actually becomes to be
published by the fix but the WSDL /definitions/service/port/soap:address/@location (XPath
notation for convenience) points to the original Web service
(
http://127.0.0.1:8080/Quickstart_webservice_producer_esb/GoodbyeWorldWS). What is
expected here should be the http-gateway endpoint on ESB
(
http://127.0.0.1:8080/Quickstart_webservice_producer/http/MyServiceCatego...)
because otherwise a client ends up calling the original Web service directly.
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL:
https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
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