Error deploying composite projects with partner links in abstract wsdl

Question

Error while deployment of PartnerLinkCompositeError. The two composites have the same wsdl files, but PartnerLinkCompositeError composite projects has a perter link inside the wsdl.
<partnerLinkType name="execute_ptt"
xmlns="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
<role name="execute_pttProvider">
<portType name="tns:execute_ptt"/>
</role>
</partnerLinkType>
The error during deployment
[04:13:04 PM] Error deploying archive sca_PartnerLinkCompositeError_rev1.0.jar to partition "default" on server soa_server1 [http://158.166.229.41:8001]
[04:13:04 PM] HTTP error code returned [500]
[04:13:04 PM] Error message from server:
There was an error deploying the composite on soa_server1: Deployment Failed: Unable to find a WSDL that has a definition for service {http://xmlns.oracle.com/EBS/PartnerLinkCompositeError/Mediator1}Mediator1_ep and port execute_pt. Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server..
[04:13:04 PM] Check server log for more details.
[04:13:04 PM] Error deploying archive sca_PartnerLinkCompositeError_rev1.0.jar to partition "default" on server soa_server1 [http://158.166.229.41:8001]
[04:13:04 PM] #### Deployment incomplete. ####
[04:13:04 PM] Error deploying archive file:/D:/workspace/NIF2/PartnerLinkCompositeError/deploy/sca_PartnerLinkCompositeError_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
What can be the cause for this error?
Projects for download
http://www.4shared.com/zip/w5R5zp1G/PartnerLinkCompositeError.html
http://www.4shared.com/zip/EM7butNF/PartnerLinkComposite.html

Answer 1

During WSDL design for composite projects like BPM or SOA using JDeveloper WSDL designer or by hand, BE sure that the partner link namespace is in the root of the wsdl definition.
<?xml version= '1.0' encoding= 'UTF-8' ?>
<wsdl:definitions name="Service"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
<wsdl:portType name="execute_ptt">
</wsdl:portType>
<wsdl:portType name="callback_ptt">
</wsdl:portType>
<plnk:partnerLinkType name="execute_ptt">
<plnk:role name="execute_pttProvider">
<plnk:portType name="tns:execute_ptt"/>
</plnk:role>
</plnk:partnerLinkType>
</wsdl:definitions>
Example:
WSDL that will deploy
<?xml version= '1.0' encoding= 'UTF-8' ?>
<wsdl:definitions name="Mediator1"
targetNamespace="http://xmlns.oracle.com/EBS/PartnerLinkCompositeError/Mediator1"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:inp1="http://xmlns.oracle.com/singleString"
xmlns:tns="http://xmlns.oracle.com/EBS/PartnerLinkCompositeError/Mediator1"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
<wsdl:types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://xmlns.oracle.com/singleString"
schemaLocation="xsd/singleString.xsd"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="requestMessage">
<wsdl:part name="request" element="inp1:singleString"/>
</wsdl:message>
<wsdl:message name="callbackMessage">
<wsdl:part name="callback" element="inp1:singleString"/>
</wsdl:message>
<wsdl:portType name="execute_ptt">
<wsdl:operation name="execute">
<wsdl:input message="tns:requestMessage"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:portType name="callback_ptt">
<wsdl:operation name="callback">
<wsdl:input message="tns:callbackMessage"/>
</wsdl:operation>
</wsdl:portType>
<plnk:partnerLinkType name="execute_ptt">
<plnk:role name="execute_pttProvider">
<plnk:portType name="tns:execute_ptt"/>
</plnk:role>
</plnk:partnerLinkType>
</wsdl:definitions>
Seems that Oracle JDeveloper WSDL designer has contribution to this issue since when trying to add a partner link from
http://www.4shared.com/photo/7D4D4Elx/wsdl_designer.html?
it creates the wsdl with the following configuration.
http://www.4shared.com/photo/zb907pXN/wsdl_designer_2.html?
Maybe will be fixed in next versions of JDeveloper. Until then, use this work suggested around.