No Such Operation failure

Question

I have a simply BPEL process, which just does an Invoke to a Partnerlink, which calls a web service on a remote server.
On execution I receive the following failure :
<remoteFault>
<part name="code" >
<code>Client</code>
</part>
<part name="summary" >
<summary>when invoking endpointAddress 'http://xxx-test/GetX, No such operation 'registrationDocument'</summary>
</part>
<part name="detail" >
<detail>AxisFault faultCode: {http://xml.apache.org/axis/}Client faultSubcode: faultString: No such operation 'registrationDocument' faultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}hostname:xxx-test </detail>
</part>
</remoteFault>
Now registrationDocument is in the <Message> section and nothing at all to do with the binding information! Input to this web service is normally a chunk of XML, but it does not even get that far.
My WSDL Validates correcly and looks like this :
<?xml version="1.0" encoding="UTF-8" ?>
- <definitions targetNamespace="http://integration.xxx.test" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:y="http://integration.xxx.test">
- <types>
<xs:schema />
</types>
- <message name="register">
<part name="registrationDocument" type="xs:string" />
</message>
- <message name="recall">
<part name="recallDocument" type="xs:string" />
</message>
- <message name="ReturnCode">
<part name="status" type="xs:int" />
</message>
- <portType name="RecallAndRegisterX">
- <operation name="registerX">
<input message="y:register" />
<output message="y:ReturnCode" />
</operation>
- <operation name="recallX">
<input message="y:recall" />
<output message="y:ReturnCode" />
</operation>
</portType>
- <binding name="bindRegisterAndRecall" type="y:RecallAndRegisterX">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
- <operation name="registerX">
<soap:operation soapAction="" style="document" />
- <input>
<soap:body use="literal" />
</input>
- <output>
<soap:body use="literal" />
</output>
</operation>
- <operation name="recallX">
<soap:operation soapAction="" style="document" />
- <input>
<soap:body use="literal" />
</input>
- <output>
<soap:body use="literal" />
</output>
</operation>
</binding>
- <service name="RecallAndRegisterX">
- <port binding="y:bindRegisterAndRecall" name="Registerandrecall">
<soap:address location="http://xxx-test/GetX" />
</port>
</service>
</definitions>
If I change registrationDocument to RegisterX my BPEL process does not fail, but simply returns xs:int
Why is BPEL ignoring the binding information? Is there something wrong with my WSDL? I can execute it from XMLSpy.
Pete

Answer 1

In your WSDL you are using the RPC-literal syntax for the parts while advertizing document-literal in the binding. This are two incompatible combinations, and most likely where BPEL fails to process the WSDL correctly.
<part name="recallDocument" type="xs:string" /> is not valid. Instead, you should be pointing at a named element in your schema section, that defines the message.
<part name="recallDocument" element="y:recall" />
<xs:schema targetNamespace="http://integration.xxx.test">
<xs:element name="recall" type="xs:string"/>
</xs:schema>
Hope this helps,
Eric