Description of problem: Platform BZ for https://issues.jboss.org/browse/JBESB-3868 When I use SOAPProcessor with HTTP Gateway, even setting the "rewrite-endpoint-url" property to false results in the endpoint URL in the published WSDL rewritten from the original one to that of the ESB. Note that with JBR Gateway (using HTTP protocol), this property can turn off the endpoint URL rewriting. How reproducible: Easy. Steps to Reproduce: 1. Pick up the "webservice_producer" quickstart and modify it to use HTTP Gateway. 2. Add the "rewrite-endpoint-url" property with false to the SOAPProcessor in the action pipeline. 3. Deploy this quickstart and confirm the endpoint URL in WSDL is rewritten through the contract web. Actual results: The endpoint URL in WSDL is rewritten. Expected results: The endpoint URL in WSDL shouldn't be rewritten.
Tadayoshi Sato <tadayosi> made a comment on jira JBESB-3868 The root cause I found is: JBossWSWebserviceContractPublisher (a publisher for SOAPProcessor) has two instances, one for ContractProvider (HTTP Gateway) and the other for Publisher (Contract Web / JBR Gateway). But only the instance for Publisher initialises the {{rewriteEndpointUrl}} field. That's why it doesn't work only for HTTP Gateway.
Tadayoshi Sato <tadayosi> updated the status of jira JBESB-3868 to Resolved
Verified in ER1
Tom Cunningham <tcunning> updated the status of jira JBESB-3868 to Closed
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.