Description of problem: Platform BZ for https://issues.jboss.org/browse/JBESB-3783 SOAPProxy should rewrite the service port addresses in WSDL provided by a target Web service endpoint from the original URL to ESB's URL. But if the target is a SOAP 1.2 service, SOAPProxy fails to rewrite its SOAP 1.2 address location and the original URL remains to be presented in the WSDL provided by ESB like below: WSDL published by ESB <definitions ... xmlns:soap12='http://schemas.xmlsoap.org/wsdl/soap12/'> ... <service name='GoodbyeWorldWSService'> <port binding='tns:GoodbyeWorldWSBinding' name='GoodbyeWorldWSPort'> <soap12:address location='http://www.acme.com/original/address'/> <!-- original Web service address, not ESB's --> </port> </service> </definitions> Additional info: (Workaround) SOAPProxy utilises Smooks internally to rewrite WSDL. So use wsdlTransform property of SOAPProxy action in jboss-esb.xml to supplement the missing transformer for SOAP 1.2. jboss-esb.xml ... <action name="soapProxy" class="org.jboss.soa.esb.actions.soap.proxy.SOAPProxy"> <property name="wsdl" value="http://www.acme.com/original/address?wsdl" /> <property name="wsdlTransform" value="/soap12-port-transformer.xml" /> </action> ... soap12-port-transformer.xml <?xml version="1.0" encoding="UTF-8"?> <smooks-resource-list xmlns="http://www.milyn.org/xsd/smooks-1.1.xsd"> <resource-config selector="port address" selector-namespace="http://schemas.xmlsoap.org/wsdl/soap12/"> <resource>org.jboss.soa.esb.actions.soap.WsdlEndpointTransformer</resource> </resource-config> </smooks-resource-list>
GSS considers this 'medium'. The case included on this ticket is now closed, but there is another customer watching the issue. Could we please examine this for SOA-P 5.3?
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Normally, the SOAPProxy will change the service port addresses in WSDL (which are provided by a target Web service endpoint) from the default settings to the ESB's URL. However, if the target is a SOAP 1.2 service, the SOAPProxy fails to rewrite its SOAP 1.2 address location and the default URL remains in the WSDL instead. To work around this issue, use the SOAPProxy action's wsdlTransform property (found in the jboss-esb.xml file) to supplement the missing transformer for SOAP 1.2. See the bug ticket for a code sample.
Max Hoo <giulianodb> made a comment on jira JBESB-3783 How can I add this patch in the jbossesb?
Hitesh Patel <sunil_patel> made a comment on jira JBESB-3783 If the action class is extended from SOAPProxy, this workaround does not work.
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.