More than one operation defined. Unable to resolve operation

Question

Hi,
Using the attached WSDL to define a BPEL sequence I allways get the following error message:
More than one operation defined. Unable to resolve operation:
This occured in the moment i introduced a seconde operation. With one operation everything works fine.
Does anybody know how to define a WSDL that works for the BPEL system with more than one operation?
Best Regards,
Axel.
WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://dummy.ws.axelbenz.de/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" targetNamespace="http://dummy.ws.axelbenz.de/" name="StringInOutService" xmlns:plink="http://schemas.xmlsoap.org/ws/2004/03/partner-link/">
<types>
<xsd:schema>
<xsd:import namespace="http://dummy.ws.axelbenz.de/" schemaLocation="upperService.xsd" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" />
</xsd:schema>
</types>
<message name="lowerMessage">
<part name="lowerParameters" type="tns:lowerType" />
</message>
<message name="lowerMessageResponse">
<part name="lowerResponseParameters" type="tns:lowerTypeResponse" />
</message>
<message name="upperMessage">
<part name="upperParameters" type="tns:upperType" />
</message>
<message name="upperMessageResponse">
<part name="upperResponseParameters" type="tns:upperTypeResponse" />
</message>
<portType name="StringInOut">
<operation name="lowerOperation">
<input message="tns:lowerMessage" />
<output message="tns:lowerMessageResponse" />
</operation>
<operation name="upperOperation">
<input message="tns:upperMessage" />
<output message="tns:upperMessageResponse" />
</operation>
</portType>
<binding name="StringInOutPortBinding" type="tns:StringInOut">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
<operation name="lowerOperation">
<soap:operation soapAction="lower" style="document" />
<input>
<soap:body use="literal" parts="lowerParameters" />
</input>
<output>
<soap:body use="literal" parts="lowerResponseParameters" />
</output>
</operation>
<operation name="upperOperation">
<soap:operation soapAction="upper" style="document" />
<input>
<soap:body use="literal" parts="upperParameters" namespace="" />
</input>
<output>
<soap:body use="literal" parts="upperResponseParameters" />
</output>
</operation>
</binding>
<service name="StringInOutService">
<port name="StringInOutPort" binding="tns:StringInOutPortBinding">
<soap:address location="http://GWBE0040.int.gematik.de:18181/DummyServices/StringInOutService" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" />
</port>
</service>
<plink:partnerLinkType name="partnerlinktype1">
<plink:role name="serviceRequestor" portType="tns:StringInOut"/>
</plink:partnerLinkType>
</definitions>
XSD:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema version="1.0" targetNamespace="http://dummy.ws.axelbenz.de/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="lower" type="ns1:lowerType" xmlns:ns1="http://dummy.ws.axelbenz.de/" />
<xs:complexType name="lowerType">
<xs:sequence>
<xs:element name="inp" type="xs:string" minOccurs="0" />
</xs:sequence>
</xs:complexType>
<xs:element name="lowerResponse" type="ns2:lowerTypeResponse" xmlns:ns2="http://dummy.ws.axelbenz.de/" />
<xs:complexType name="lowerTypeResponse">
<xs:sequence>
<xs:element name="return" type="xs:string" minOccurs="0" />
</xs:sequence>
</xs:complexType>
<xs:element name="upper" type="ns3:upperType" xmlns:ns3="http://dummy.ws.axelbenz.de/" />
<xs:complexType name="upperType">
<xs:sequence>
<xs:element name="inp" type="xs:string" minOccurs="0" />
</xs:sequence>
</xs:complexType>
<xs:element name="upperResponse" type="ns4:upperTypeResponse" xmlns:ns4="http://dummy.ws.axelbenz.de/" />
<xs:complexType name="upperTypeResponse">
<xs:sequence>
<xs:element name="return" type="xs:string" minOccurs="0" />
</xs:sequence>
</xs:complexType>
</xs:schema>

Answer 1

What client are you using? Are you using the netbeans enterprise pack test driver? If so, you can set the soap action in the test properties to match the ones you have defined in the WSDL.
Also if you could post the actual soap message you are sending that would help.
I also noticed that you're using parts defined via types with a document/literal binding. To be more basic profile compliant in that casue you may want to use RPC style instead - it is not strictly necessary, but increases interoperability.
Andi