Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 813138

Summary:	SOAPProxy doesn't rewrite SOAP1.2 service port address location in WSDL
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Tadayoshi Sato <tasato>
Component:	JBossESB	Assignee:	Nobody <nobody>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	5.2.0 GA	CC:	ldimaggi, soa-p-jira
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	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.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 03:19:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tadayoshi Sato 2012-04-17 03:45:49 UTC

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>

Comment 2 Rick Wagner 2012-05-11 13:52:42 UTC

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?

Comment 3 David Le Sage 2012-06-12 05:46:31 UTC

    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.

Comment 4 JBoss JIRA Server 2012-09-12 18:31:49 UTC

Max Hoo <giulianodb> made a comment on jira JBESB-3783

How can I add this patch in the jbossesb?

Comment 5 JBoss JIRA Server 2012-09-17 15:17:55 UTC

Hitesh Patel <sunil_patel> made a comment on jira JBESB-3783

If the action class is extended from SOAPProxy, this workaround does not work.

Comment 10 Red Hat Bugzilla 2025-02-10 03:19:36 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.