[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
Magesh Bojan commented on JBESB-3789:
-------------------------------------
Jason,
The SOAPProcessor is an action that exposes only Webservice endpoints that are internally
hosted in the same container via JBossWS. This JIRA was created to mimic the behavior of
JBR gateway in the new HTTP gateway. That has been done along with the endpoint address
rewrite. Please do not overwhelm the issue here.
Just rewriting schema urls alone will not work, as such the resources like
http://myTestServer/myapp-esb-myapp-esb-ws-0.7.0-SNAPSHOT/myapp?xsd=myapp... do not exist
in the server. The schema or WSDL imports will always point to the original
Webservice's location only as done by JBR gateway. This needs to be handled in a
separate JIRA. This encloses rewriting all JBR, HTTP gateway schema import urls and
caching the schemas. Whether this feature will be acceptable or not we need to validate
that separately. Users can inline their schema for the time being.
Tadayoshi,
The SOAP1.2 support is not there in SOAPProcessor/SOAPProxy as of now. The linked issue
only states one small portion of re-writing that is not happening. That is definitely not
related to this schema re-writing issue at all although they may touch the same files.
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