ESB WSDL generation and compatibility issues

Question

Hi all.
I have a need to integrate Oracle ESB with TIBCO, and I'm facing some issues regarding the use of namespaces in WSDL.
In ESB, when I create a routing service, its corresponding WSDL has a targetNamespace attribute, for example, http://www.oracle.com/myRS
When I deploy this routing service using the "Invokable from external services" property checked, ESB automatically generates another WSDL, which contains the SOAP and ESB bindings and imports the previous WSDL. This WSDL's targetNamespace has the same value of the targetNamespace from the previous WSDL (http://www.oracle.com/myRS)
When TIBCO needs to consume the ESB web service ( the automatically generated one), it's complaining that the two WSDLs have the same targetNamespace, and they shouldn't (according to them).
Here's is an example:
1 - I create a routing service. It's WSDL looks like this:
<definitions name="TIBCOIntegrationRS" targetNamespace="http://oracle.com/esb/namespaces/TIBCOIntegration" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://oracle.com/esb/namespaces/TIBCOIntegration" xmlns:inp1="http://xmlns.oracle.com/pcbpel/adapter/db/top/CvrdRaCustomersIFace">
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/pcbpel/adapter/db/top/CvrdRaCustomersIFace" schemaLocation="CvrdRaCustomersIFace_table.xsd"/>
</schema>
</types>
<message name="CvrdRaCustomersIface_request">
<part name="CvrdRaCustomersIface" element="inp1:CvrdRaCustomersIface"/>
</message>
<portType name="execute_ppt">
<operation name="execute">
<input message="tns:CvrdRaCustomersIface_request"/>
</operation>
</portType>
</definitions>
2 - I deploy the routing service, and get another WSDL that is automatically generated:
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:import="http://oracle.com/esb/namespaces/TIBCOIntegration" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:esb="http://www.oracle.com/esb/" xmlns:ws="http://www.example.com/webservice" xmlns:tns="http://oracle.com/esb/namespaces/TIBCOIntegration" targetNamespace="http://oracle.com/esb/namespaces/TIBCOIntegration">
<import namespace="http://oracle.com/esb/namespaces/TIBCOIntegration" location="http://denis:80/esb/slide/ESB_Projects/DadosCliente_TIBCOIntegrationESB/TIBCOIntegration_TIBCOIntegrationRS.wsdl"/>
<portType name="execute_ppt">
<operation name="execute">
<input message="tns:CvrdRaCustomersIface_request"/>
</operation>
</portType>
<binding name="__esb_TIBCOIntegrationRS_execute_ppt" type="tns:execute_ppt">
<esb:binding/>
<operation name="execute">
<esb:operation event-name="TIBCOIntegration.TIBCOIntegrationRS.execute"/>
<input/>
</operation>
</binding>
<binding name="__soap_TIBCOIntegrationRS_execute_ppt" type="tns:execute_ppt">
<soap:binding xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="execute">
<soap:operation xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" style="document" soapAction="execute"/>
<input>
<soap:body xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" use="literal"/>
</input>
</operation>
</binding>
<service name="ESB_TIBCOIntegrationRS_Service">
<port name="__soap_TIBCOIntegrationRS_execute_ppt" binding="tns:__soap_TIBCOIntegrationRS_execute_ppt">
<soap:address xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" location="http://denis:80/event/TIBCOIntegration/TIBCOIntegrationRS"/>
</port>
<port name="__esb_TIBCOIntegrationRS_execute_ppt" binding="tns:__esb_TIBCOIntegrationRS_execute_ppt">
</port>
</service>
<plt:partnerLinkType name="execute_pptLT">
<plt:role name="execute_pptProvider">
<plt:portType name="tns:execute_ppt"/>
</plt:role>
</plt:partnerLinkType>
</definitions>
3 - We can see that both WSDLs have the same targetNamespace, and that's what TIBCO is complaining about.
I've been reading the W3C WSDL spec (2.0), and found a note regarding the use of the import clause in WSDL:
http://www.w3.org/TR/2007/REC-wsdl20-20070626/#import_namespace_attribute
It has the following fragment:
"The namespace attribute information item is of type xs:anyURI. Its actual value indicates that the containing WSDL 2.0 document MAY contain qualified references to WSDL 2.0 components in that namespace (via one or more prefixes declared with namespace declarations in the normal way). This value MUST NOT match the actual value of targetNamespace attribute information item in the enclosing WSDL 2.0 document"
I don't know if ESB is currently working with WSDL 2.0 specification. I's mentioned here just for a comparison.
So, the question is: Is it allowed and W3C compatible to use the same targetNamespace in the enclosing WSDL as well as in the imported one?
thanks
Denis
Message was edited by:
[email protected]
Message was edited by:
[email protected]

Answer 1

Hi ,
This is Shobana K from PeopleTools.
I am also facing a similar issue.
The ESB services exposed for external invocation are nested wsdls meaning one WSDL imports another.
Consider this nested WSDL for example-
http://10.176.162.55:8888/esb/wsil/NestedESB_synchronous/NestedSynch_RS?wsdl
Above wsdl corresponds to the base wsdl containing the binding and service information. This in turn imports another WSDL http://10.176.162.55:8888/esb/slide/ESB_Projects/8.50_ESB_Nested_wsdl_NestedESB_synchronous/NestedESB_synchronous_NestedSynch_RS.wsdl
which contains port type, message and schema information. These wsdls are formed in accordance to the "import authoring style" defined in 2.1.2 section of the WSDL1.1 specification.
The authoring style used in ESB wsdl is exactly the same as the one shown in the WSDL spec but for one point.
In case of ESB, both the wsdls(base as well as the imported one) have the same target namespace. Is it possible for 2 wsdls to have the same target namespace within the same scope?
In order to parse the WSDL for the required information, we need to look at the information both in the base wsdl as well as the imported wsdl. While trying to locate the correct information in the right wsdl, we make use of the namespace value used with the element name. For e.g, the base wsdl may only be containing the binding information. This in turn will refer to the port type information available in the imported wsdl. Now, while parsing, we make use of the namespace value associated with the port type element name in the base wsdl.Based on the namespace value, we decide which wsdl contains this information.
In the sample nested ESB wsdl that I have quoted above http://10.176.162.55:8888/esb/slide/ESB_Projects/8.50_ESB_Nested_wsdl_NestedESB_synchronous/NestedESB_synchronous_NestedSynch_RS.wsdl, the tns(this namespace) value associated with the port type element corresponds to the target namespace value in both the wsdls and the value happens to be the same. Hence while parsing, when we look for the port type and message information belonging to the "tns" namespace, we tend to search for those information only in the base wsdl and not the imported one.This sounds logical and it would have worked had the target namespace been different for the 2 wsdls. It fails in this case because both the WSDLs have the same target namespace. In such cases, how should we go about parsing the wsdl?
Your inputs and feedback will be greatly appreciated.
Thanks a lot in advance.
Regards,
Shobana K