I have also the same problem. When I use soapUI to test my BPEL I have the
following error:
org.apache.ode.axis2.OdeFault: SOAP body does not contain expected part
wrapper: service
{http://j2ee.netbeans.org/wsdl/Ehealth1/ehealth1}ehealth1Service port
ehealth1CallPortTypeBindingPort wrapper ehealth1CallOperationhere is the WSDL: <?xml version="1.0" encoding="UTF-8"?> <definitions name="ehealth1" targetNamespace="http://j2ee.netbeans.org/wsdl/Ehealth1/ehealth1" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://j2ee.netbeans.org/wsdl/Ehealth1/ehealth1" xmlns:ns0="http://stockageRSW.ehealth.org" xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"> <import location="StockageRSW.wsdl" namespace="http://stockageRSW.ehealth.org"/> <types/> <message name="CallOperationRequest"> <part name="part1" type="xsd:string"/> </message> <message name="CallOperationResponse"> <part name="part1" type="xsd:string"/> </message> <portType name="ehealth1CallPortType"> <operation name="ehealth1CallOperation"> <input name="input1" message="tns:CallOperationRequest"/> <output name="output1" message="tns:CallOperationResponse"/> </operation> </portType> <binding name="ehealth1CallPortTypeBinding" type="tns:ehealth1CallPortType"> <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/> <operation name="ehealth1CallOperation"> <soap:operation style="rpc"/> <input name="input1"> <soap:body use="literal"/> </input> <output name="output1"> <soap:body use="literal"/> </output> </operation> </binding> <service name="ehealth1Service"> <port name="ehealth1CallPortTypeBindingPort" binding="tns:ehealth1CallPortTypeBinding"> <soap:address location="http://localhost:8080/ode/processes/ehealth1"/> </port> </service> <plnk:partnerLinkType name="ehealth1"> <!-- A partner link type is automatically generated when a new port type is added. Partner link types are used by BPEL processes. In a BPEL process, a partner link represents the interaction between the BPEL process and a partner service. Each partner link is associated with a partner link type. A partner link type characterizes the conversational relationship between two services. The partner link type can have one or two roles.--> <plnk:role name="ehealth1CallPortTypeRole" portType="tns:ehealth1CallPortType"/> </plnk:partnerLinkType> </definitions> and here is the request done by soapUI: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ehe="http://j2ee.netbeans.org/wsdl/Ehealth1/ehealth1"> <soapenv:Header/> <soapenv:Body> <ehe:ehealth1CallOperation> <part1>hello</part1> </ehe:ehealth1CallOperation> </soapenv:Body> </soapenv:Envelope> Any idea? Thanks a lot Fabian. -- View this message in context: http://old.nabble.com/SOAP-body-does-not-contain-expected-part-wrapper%21-tp20183513p28068320.html Sent from the Apache Ode User mailing list archive at Nabble.com.
