Javax.jbi.messaging.MessagingException: More than one operation defined

Hi,
i had already implemented a web service consisting of 6 methods that works fine. Now i want to access this service via JBI. Therefore i developed a service assembly containing only of a soap binding component. When i try to access the jbi environment via the inbound endpoint OpenESB throws following exception:
[#|2006-07-26T16:23:50.531+0200|WARNING|sun-appserver-pe9.0|com.sun.jbi.component.com.sun.httpsoapbc-1.0-2com.sun.jbi.httpsoapbc.embedded.GrizzlyRequestProcessor|_ThreadID=32;_ThreadName=httpWorkerThread-12010-2;_RequestID=a33dbb24-d088-4a6a-9642-96187c32bb36;|Exception in processing request.
javax.jbi.messaging.MessagingException: More than one operation defined. Unable to resolve operation: {http://service}UseRepositoryService,UseRepository,inbound
     at com.sun.jbi.httpsoapbc.InboundMessageProcessor.execute(InboundMessageProcessor.java:214)
     at com.sun.jbi.httpsoapbc.embedded.GrizzlyRequestProcessor.processAsynchRequest(GrizzlyRequestProcessor.java:214)
     at com.sun.jbi.httpsoapbc.embedded.GrizzlyRequestProcessor.service(GrizzlyRequestProcessor.java:173)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
     at com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:70)
     at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:143)
     at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:132)
     at com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:81)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
     at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
How can i specify in my service assembly that if i send a SOAP request for method X on my client that OpenESB routes this message to the correct Outbound endpoint?
Thank you
Thomas

Hello Andi,
thanks for your reply. To exclude the soap action error i will post the complete wsdl file now. But in my opinion every operation has its own input and output definition.
The consumer wsdl:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://service" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://service" xmlns:intf="http://service" xmlns:tns1="http://types" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<wsdl:types>
<schema elementFormDefault="qualified" targetNamespace="http://service" xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://types"/>
<element name="loadEcore">
<complexType>
<sequence>
<element name="ecoreId" type="xsd:long"/>
</sequence>a
</complexType>
</element>
<element name="loadEcoreResponse">
<complexType>
<sequence>
<element name="loadEcoreReturn" type="xsd:base64Binary"/>
</sequence>
</complexType>
</element>
<element name="loadInstance">
<complexType>
<sequence>
<element name="instanceId" type="xsd:long"/>
</sequence>
</complexType>
</element>
<element name="loadInstanceResponse">
<complexType>
<sequence>
<element name="loadInstanceReturn" type="xsd:base64Binary"/>
</sequence>
</complexType>
</element>
<element name="loadInstanceForProject">
<complexType>
<sequence>
<element name="instanceId" type="xsd:long"/>
</sequence>
</complexType>
</element>
<element name="loadInstanceForProjectResponse">
<complexType>
<sequence>
<element name="loadInstanceForProjectReturn" type="xsd:base64Binary"/>
</sequence>
</complexType>
</element>
<element name="deleteInstance">
<complexType>
<sequence>
<element name="instanceId" type="xsd:long"/>
</sequence>
</complexType>
</element>
<element name="deleteInstanceResponse">
<complexType>
<sequence>
<element name="deleteInstanceReturn" type="xsd:boolean"/>
</sequence>
</complexType>
</element>
<element name="getAllInstancesFromDB">
<complexType/>
</element>
<element name="getAllInstancesFromDBResponse">
<complexType>
<sequence>
<element maxOccurs="unbounded" name="getAllInstancesFromDBReturn" type="tns1:InstancePackageValueBean"/>
</sequence>
</complexType>
</element>
<element name="saveInstance">
<complexType>
<sequence>
<element name="resourceBytes" type="xsd:base64Binary"/>
<element name="fileName" type="xsd:string"/>
</sequence>
</complexType>
</element>
<element name="saveInstanceResponse">
<complexType>
<sequence>
<element name="saveInstanceReturn" type="xsd:boolean"/>
</sequence>
</complexType>
</element>
</schema>
<schema elementFormDefault="qualified" targetNamespace="http://types" xmlns="http://www.w3.org/2001/XMLSchema">
<complexType name="InstancePackageValueBean">
<sequence>
<element name="ecoreId" type="xsd:long"/>
<element name="fileName" nillable="true" type="xsd:string"/>
<element name="id" type="xsd:long"/>
<element name="name" nillable="true" type="xsd:string"/>
<element name="usedModels" nillable="true" type="xsd:string"/>
</sequence>
</complexType>
</schema>
</wsdl:types>
<wsdl:message name="loadEcoreRequest">
<wsdl:part element="impl:loadEcore" name="parameters"/>
</wsdl:message>
<wsdl:message name="loadEcoreResponse">
<wsdl:part element="impl:loadEcoreResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="saveInstanceResponse">
<wsdl:part element="impl:saveInstanceResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="loadInstanceForProjectResponse">
<wsdl:part element="impl:loadInstanceForProjectResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="loadInstanceResponse">
<wsdl:part element="impl:loadInstanceResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="getAllInstancesFromDBRequest">
<wsdl:part element="impl:getAllInstancesFromDB" name="parameters"/>
</wsdl:message>
<wsdl:message name="loadInstanceRequest">
<wsdl:part element="impl:loadInstance" name="parameters"/>
</wsdl:message>
<wsdl:message name="getAllInstancesFromDBResponse">
<wsdl:part element="impl:getAllInstancesFromDBResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="loadInstanceForProjectRequest">
<wsdl:part element="impl:loadInstanceForProject" name="parameters"/>
</wsdl:message>
<wsdl:message name="saveInstanceRequest">
<wsdl:part element="impl:saveInstance" name="parameters"/>
</wsdl:message>
<wsdl:message name="deleteInstanceRequest">
<wsdl:part element="impl:deleteInstance" name="parameters"/>
</wsdl:message>
<wsdl:message name="deleteInstanceResponse">
<wsdl:part element="impl:deleteInstanceResponse" name="parameters"/>
</wsdl:message>
<wsdl:portType name="UseRepository">
<wsdl:operation name="loadEcore">
<wsdl:input message="impl:loadEcoreRequest" name="loadEcoreRequest"/>
<wsdl:output message="impl:loadEcoreResponse" name="loadEcoreResponse"/>
</wsdl:operation>
<wsdl:operation name="loadInstance">
<wsdl:input message="impl:loadInstanceRequest" name="loadInstanceRequest"/>
<wsdl:output message="impl:loadInstanceResponse" name="loadInstanceResponse"/>
</wsdl:operation>
<wsdl:operation name="loadInstanceForProject">
<wsdl:input message="impl:loadInstanceForProjectRequest" name="loadInstanceForProjectRequest"/>
<wsdl:output message="impl:loadInstanceForProjectResponse" name="loadInstanceForProjectResponse"/>
</wsdl:operation>
<wsdl:operation name="deleteInstance">
<wsdl:input message="impl:deleteInstanceRequest" name="deleteInstanceRequest"/>
<wsdl:output message="impl:deleteInstanceResponse" name="deleteInstanceResponse"/>
</wsdl:operation>
<wsdl:operation name="getAllInstancesFromDB">
<wsdl:input message="impl:getAllInstancesFromDBRequest" name="getAllInstancesFromDBRequest"/>
<wsdl:output message="impl:getAllInstancesFromDBResponse" name="getAllInstancesFromDBResponse"/>
</wsdl:operation>
<wsdl:operation name="saveInstance">
<wsdl:input message="impl:saveInstanceRequest" name="saveInstanceRequest"/>
<wsdl:output message="impl:saveInstanceResponse" name="saveInstanceResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="UseRepositorySoapBinding" type="impl:UseRepository">
<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="loadEcore">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="loadEcoreRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="loadEcoreResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="loadInstance">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="loadInstanceRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="loadInstanceResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="loadInstanceForProject">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="loadInstanceForProjectRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="loadInstanceForProjectResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="deleteInstance">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="deleteInstanceRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="deleteInstanceResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="getAllInstancesFromDB">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="getAllInstancesFromDBRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="getAllInstancesFromDBResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="saveInstance">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="saveInstanceRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="saveInstanceResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="UseRepositoryService">
<wsdl:port binding="impl:UseRepositorySoapBinding" name="UseRepository">
<wsdlsoap:address location="http://localhost:12010/service/repository"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Except for the service name, port, address etc the provider wsdl is the same.
Could you tell me if it works when i will only use one operation for example?
I had already implemented a service assembly which contained only one operation. That SA worked fine.
If the Service Assembly and Binding Component descriptors had wrong references e.g. the wrong interface-name, would OpenESB throws an exception while deployment?
In addition, could you tell me a good link to a nice bpel engine example? How is the interaction between client ans service using the bpel engine?
I think using the SoapBC the interaction is following:
Client --> BC --> Service
With Bpel engine?
Client --> BC --> bpel --> BC2 --> service?
Thanks a lot
Thomas

Similar Messages

More than one operation defined. Unable to resolve operation

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>

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

Javax.jbi.messaging.MessagingException: Unable to locate the operation

Hi,
I'm getting the following expection when try to test a built and deployed composite application:
javax.jbi.messaging.MessagingException: Unable to locate the operation that has the matching message signature in the requested endpoint {tmf854.v1.ws}ServiceProvisioning,ServiceProvisioningHttp,inbound as in the input SOAP body.
This doesn't make sense, as the Glassfish log shows:
Prepared inbound endpoint {tmf854.v1.ws}ServiceProvisioning,ServiceProvisioningHttp,inbound mapped to context /ServiceProvisioning/Common.
Below is the WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tmf854WS="tmf854.v1.ws"
                  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                  xmlns:tmf854XSD="tmf854.v1"
                  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
                  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
                  xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
                  targetNamespace="tmf854.v1.ws"
                  name="IhugProvisioningService"
                  xmlns:ns1="tmf854.v1"
                  xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype"
                  xmlns:vprop="http://docs.oasis-open.org/wsbpel/2.0/varprop">
    
    <wsdl:types>
        <xsd:schema targetNamespace="tmf854.v1.ws">
            <xsd:import namespace="tmf854.v1" schemaLocation="Header.xsd"/>
            <xsd:import namespace="tmf854.v1" schemaLocation="Exceptions.xsd"/>
            <xsd:import namespace="tmf854.v1" schemaLocation="IHugServiceProvisioning.xsd"/>
        </xsd:schema>
    </wsdl:types>
    
    <wsdl:message name="ProcessingFailureException">
        <wsdl:documentation>
            The generic exception message.
        </wsdl:documentation>
        <wsdl:part name="ProcessingFailureException" element="tmf854XSD:ProcessingFailureException"/>
    </wsdl:message>
    
    <wsdl:message name="getAvailableServicesByLWC">
        <wsdl:documentation>
            The getInventory request message.
        </wsdl:documentation>
        <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
        <wsdl:part name="mtosiBody" element="tmf854XSD:getServicesByExchangeID"/>
    </wsdl:message>
    <wsdl:message name="getAvailableServicesByLWCResponse">
        <wsdl:documentation>
            The getInventory response message.
        </wsdl:documentation>
        <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
        <wsdl:part name="mtosiBody" element="tmf854XSD:getServicesByExchangeIDResponse"/>
    </wsdl:message>
    
    <wsdl:message name="configureService">
        <wsdl:documentation>
            The configureService request message.
        </wsdl:documentation>
        <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
        <wsdl:part name="mtosiBody" element="tmf854XSD:configureService"/>
    </wsdl:message>
    <wsdl:message name="configureServiceResponse">
        <wsdl:documentation>
            The configureService response message.
        </wsdl:documentation>
        <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
        <wsdl:part name="mtosiBody" element="tmf854XSD:configureServiceResponse"/>
    </wsdl:message>
    
    <wsdl:message name="getServiceDetails">
        <wsdl:documentation>
            The getServiceDetails request message.
        </wsdl:documentation>
        <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
        <wsdl:part name="mtosiBody" element="tmf854XSD:getServiceDetails"/>
    </wsdl:message>
    <wsdl:message name="getServiceDetailsResponse">
        <wsdl:documentation>
            The getServiceDetails response message.
        </wsdl:documentation>
        <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
        <wsdl:part name="mtosiBody" element="tmf854XSD:getServiceDetailsResponse"/>
    </wsdl:message>
    
    <wsdl:message name="testService">
        <wsdl:documentation>
            The testService request message.
        </wsdl:documentation>
        <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
        <wsdl:part name="mtosiBody" element="tmf854XSD:testService"/>
    </wsdl:message>
    <wsdl:message name="testServiceResponse">
        <wsdl:documentation>
            The testService response message.
        </wsdl:documentation>
        <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
        <wsdl:part name="mtosiBody" element="tmf854XSD:testServiceResponse"/>
    </wsdl:message>
    
    <wsdl:message name="restartService">
        <wsdl:documentation>
            The restartService request message.
        </wsdl:documentation>
        <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
        <wsdl:part name="mtosiBody" element="tmf854XSD:restartService"/>
    </wsdl:message>
    <wsdl:message name="restartServiceResponse">
        <wsdl:documentation>
            The restartService response message.
        </wsdl:documentation>
        <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
        <wsdl:part name="mtosiBody" element="tmf854XSD:restartServiceResponse"/>
    </wsdl:message>
    <wsdl:message name="ServiceProvisioningOperationRequest">
        <wsdl:part name="part1" type="xsd:string"/>
    </wsdl:message>
    <wsdl:message name="ServiceProvisioningOperationReply">
        <wsdl:part name="part1" type="xsd:string"/>
    </wsdl:message>
    
    <wsdl:message name="portReservation">
        <wsdl:documentation>
            The portReservation request message.
        </wsdl:documentation>
        <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
        <wsdl:part name="mtosiBody" element="tmf854XSD:portReservation"/>
    </wsdl:message>
    <wsdl:message name="portReservationResponse">
        <wsdl:documentation>
            The portReservation response message.
        </wsdl:documentation>
        <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
        <wsdl:part name="mtosiBody" element="tmf854XSD:portReservationResponse"/>
    </wsdl:message>
    
    
    
    <wsdl:portType name="ServiceProvisioningPortType">
        <wsdl:documentation>
            The Available Services porttype
        </wsdl:documentation>
        <wsdl:operation name="GetAvailableServicesByLWCOperation">
            <wsdl:documentation>
                This is the getInventory request/response operation.
            </wsdl:documentation>
            <wsdl:input message="tmf854WS:getAvailableServicesByLWC"/>
            <wsdl:output message="tmf854WS:getAvailableServicesByLWCResponse"/>
            <wsdl:fault name="ProcessingFailureException" message="tmf854WS:ProcessingFailureException"/>
        </wsdl:operation>
        <wsdl:operation name="ConfigureServiceOperation">
            <wsdl:documentation>
                This is the configureService request/response operation.
            </wsdl:documentation>
            <wsdl:input message="tmf854WS:configureService"/>
            <wsdl:output message="tmf854WS:configureServiceResponse"/>
            <wsdl:fault name="ProcessingFailureException" message="tmf854WS:ProcessingFailureException"/>
        </wsdl:operation>
        <wsdl:operation name="GetServiceDetailsOperation">
            <wsdl:input message="tmf854WS:getServiceDetails"/>
            <wsdl:output message="tmf854WS:getServiceDetailsResponse"/>
            <wsdl:fault name="ProcessingFailureException" message="tmf854WS:ProcessingFailureException"/>
        </wsdl:operation>
        <wsdl:operation name="TestServiceOperation">
            <wsdl:input message="tmf854WS:testService"/>
            <wsdl:output message="tmf854WS:testServiceResponse"/>
            <wsdl:fault name="ProcessingFailureException" message="tmf854WS:ProcessingFailureException"/>
        </wsdl:operation>
        <wsdl:operation name="RestartServiceOperation">
            <wsdl:input message="tmf854WS:restartService"/>
            <wsdl:output message="tmf854WS:restartServiceResponse"/>
            <wsdl:fault name="ProcessingFailureException" message="tmf854WS:ProcessingFailureException"/>
        </wsdl:operation>
        <wsdl:operation name="PortReservationOperation">
            <wsdl:input message="tmf854WS:portReservation"/>
            <wsdl:output message="tmf854WS:portReservationResponse"/>
            <wsdl:fault name="ProcessingFailureException" message="tmf854WS:ProcessingFailureException"/>
        </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="ServiceProvisioningSoapHTTPBinding" type="tmf854WS:ServiceProvisioningPortType">
        <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
        <wsdl:operation name="GetAvailableServicesByLWCOperation">
            <soap:operation soapAction="getAvailableServicesByLWC"/>
            <wsdl:input>
                <soap:header message="tmf854WS:getAvailableServicesByLWC" part="mtosiHeader" use="literal" />
                <soap:body parts="mtosiBody" use="literal" />
            </wsdl:input>
            <wsdl:output>
                <soap:header message="tmf854WS:getAvailableServicesByLWCResponse" part="mtosiHeader" use="literal" />
                <soap:body parts="mtosiBody" use="literal" />
            </wsdl:output>
            <wsdl:fault name="ProcessingFailureException">
                <soap:fault name="ProcessingFailureException" use="literal" />
            </wsdl:fault>
        </wsdl:operation>
        <wsdl:operation name="ConfigureServiceOperation">
            <soap:operation soapAction="ConfigureServiceOperation"/>
            <wsdl:input>
                <soap:header message="tmf854WS:configureService" part="mtosiHeader" use="literal" />
                <soap:body parts="mtosiBody" use="literal" />
            </wsdl:input>
            <wsdl:output>
                <soap:header message="tmf854WS:configureServiceResponse" part="mtosiHeader" use="literal" />
                <soap:body parts="mtosiBody" use="literal" />
            </wsdl:output>
            <wsdl:fault name="ProcessingFailureException">
                <soap:fault use="literal" name="ProcessingFailureException" />
            </wsdl:fault>
        </wsdl:operation>
        <wsdl:operation name="GetServiceDetailsOperation">
            <soap:operation soapAction="GetServiceDetailsOperation"/>
            <wsdl:input>
                <soap:header message="tmf854WS:getServiceDetails" part="mtosiHeader" use="literal" />
                <soap:body parts="mtosiBody" use="literal" />
            </wsdl:input>
            <wsdl:output>
                <soap:header message="tmf854WS:getServiceDetailsResponse" part="mtosiHeader" use="literal" />
                <soap:body parts="mtosiBody" use="literal" />
            </wsdl:output>
            <wsdl:fault name="ProcessingFailureException">
                <soap:fault use="literal" name="ProcessingFailureException" />
            </wsdl:fault>
        </wsdl:operation>
        <wsdl:operation name="TestServiceOperation">
            <soap:operation soapAction="TestServiceOperation"/>
            <wsdl:input>
                <soap:header message="tmf854WS:testService" part="mtosiHeader" use="literal" />
                <soap:body parts="mtosiBody" use="literal" />
            </wsdl:input>
            <wsdl:output>
                <soap:header message="tmf854WS:testServiceResponse" part="mtosiHeader" use="literal" />
                <soap:body parts="mtosiBody" use="literal" />
            </wsdl:output>
            <wsdl:fault name="ProcessingFailureException">
                <soap:fault use="literal" name="ProcessingFailureException" />
            </wsdl:fault>
        </wsdl:operation>
        <wsdl:operation name="RestartServiceOperation">
            <soap:operation soapAction="RestartServiceOperation"/>
            <wsdl:input>
                <soap:header message="tmf854WS:restartService" part="mtosiHeader" use="literal" />
                <soap:body parts="mtosiBody" use="literal" />
            </wsdl:input>
            <wsdl:output>
                <soap:header message="tmf854WS:restartServiceResponse" part="mtosiHeader" use="literal" />
                <soap:body parts="mtosiBody" use="literal" />
            </wsdl:output>
            <wsdl:fault name="ProcessingFailureException">
                <soap:fault use="literal" name="ProcessingFailureException" />
            </wsdl:fault>
        </wsdl:operation>
        <wsdl:operation name="PortReservationOperation">
            <soap:operation soapAction="PortReservationOperation"/>
            <wsdl:input>
                <soap:header message="tmf854WS:portReservation" part="mtosiHeader" use="literal" />
                <soap:body parts="mtosiBody" use="literal" />
            </wsdl:input>
            <wsdl:output>
                <soap:header message="tmf854WS:portReservationResponse" part="mtosiHeader" use="literal" />
                <soap:body parts="mtosiBody" use="literal" />
            </wsdl:output>
            <wsdl:fault name="ProcessingFailureException">
                <soap:fault use="literal" name="ProcessingFailureException" />
            </wsdl:fault>
        </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="ServiceProvisioning">
        <wsdl:port name="ServiceProvisioningHttp" binding="tmf854WS:ServiceProvisioningSoapHTTPBinding">
            <soap:address location="http://localhost:18181/ServiceProvisioning/Common"/>
        </wsdl:port>
    </wsdl:service>
    <vprop:property name="CorrelationToken" type="xsd:string"/>
    <vprop:propertyAlias propertyName="tmf854WS:CorrelationToken" messageType="tmf854WS:configureService" part="mtosiHeader"/>
    <plnk:partnerLinkType name="IhugServiceProvisioning">
        <plnk:role name="Requestor" portType="tmf854WS:ServiceProvisioningPortType"/>
        <plnk:role name="Service" portType="tmf854WS:ServiceProvisioningPortType"/>
    </plnk:partnerLinkType>
</wsdl:definitions>Any ideas how to resolve this?
Regards,

The problem was the generated test SOAP message from Netbeans. When built, the interface had more levels than described below. I've also had similar issues caused by bad namespaces - either not defined properly or not picking up the default namespace.

Service interface with more than one operation

Hi all,
is it possible to have a service interface with more than one operation?
I have found this blog:
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414900)ID0209118050DB10459657028039341762End?blog=/pub/wlg/15123
But this sentence:
ABAP proxy (inbound/ outbound) cannot be developed out of a Service Interface having Operations with different type of messages included. If an ABAP proxy is to be developed then all the messages included should be of one type i.e. either the included messages should be Message Type, External Message, IDOC or RFC Message. This behavior can be observed when a Service Interface is created and then subjected for a check
regards

Hi,
now the interface is running but I get another error in .NET.
"The header 'Diagnostic' from the namespace 'http://sap.com/xi/XI/Message/30' was not understood by the recipient of this message, causing the message to not be processed. This error typically indicates that the sender of this message has enabled a communication protocol that the receiver cannot process. Please ensure that the configuration of the client's binding is consistent with the service's binding. "
Any ideas?
regards

Publish more than one operation by WebService

Hi all
Somebody can helpme saying me how to do the following with eGate ( i cant use eInsight ):
For now im enabled to publish one operation and one webservice, but mi problem is that i can't publish one WebService with more than one operation and i can't change the mandatory "ExecutePortType", all my webservices url are in the form:
http://<server>:<port>/myws/ExecutePortType
1. Why the context name is about the WebService and why ExecutePortType is mandatory ?
2. I can't publish a Web Service with more than one operation ( The documentation says that the ExecutePortType supports just one operation )?
some body can helpme with an example ?

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

Forwarding messages to more than one person at a time, how in the heck do i do it ??

I recently got a new phone, and am trying to learn how to send messages to more than one person at a time. It is a Samsung Gem.
Thanks so much people,
Gayle

Gayle1963 wrote:
I recently got a new phone, and am trying to learn how to send messages to more than one person at a time. It is a Samsung Gem.
Thanks so much people,
Gayle
Hi there!
I hope you are enjoying your new phone.
In order to forward a text message to multiple people, just long-press on the message you want to send and select 'Forward'. In the 'To:' field begin typing the first persons name, then hit the 'enter' key. This will typically move the cursor down to the message, just tap on the 'To:' field again and begin typing the second person's name, and so on and so forth until you get all the people included.
Keep in mind, if you have a limited texting package that sent messages are billed per recipient. Example, if you forward a text to 10 people, then 10 messages go against the allowance.
Have a great day!

Why can't I send a text message to more than one contact?

With all my previous cell phones I was able to send a single text message to more than one contact. With the iPhone I can only send to one contact and then I have to type the text message again and send to another contact, and so on. Or am I messing a fuction on the iPhone that allows for sending a text message to more than one contact?

No, you are not missing it. That feature is not available on the iPhone.

HT3529 How do you send message to more than one address, iPhone 5, 6.0.1/

How do you send message to more than one address on iphone 5, 6.0.1?

... or, once the first address appears as a bubble, simply start typing the second address in the "To" field.

Sending a Text Message to More Than One Person...

How do i send a single text message to more than one person? Is that possible?

Not possible at present. It's on the list of feature requests. We hope an update will add this feature in the near future.

Assignment of components to more than one operation in routing.

Hi to all,
I am trying to allocate components of material BoM to more than one operation in routing. I know one way to do it is to define that components again & agin in material BoM & assigned them to operations in routing. Are other ways available to do the same.
Thanks & regards,
Abu Arbab

Dear,
Now I am clear.
You need to create different 2 BOM and with BOM items, as below,
example - total requirement of material A is say 10.
Semi finished Product- X BOM
BOM item 1 - material A-qty 8
BOM item 2 - material B-qty -5
Finished material Y - BOM
BOM item 1 - semifished material X-qty 10
BOM item 2 - material C-qty 10
BOM item 3 - material A-qty 2
BOM item 4 - material D-qty -2
You need to create above 2 BOM's if you want to see semifished product into inventory, if not proceed as below
Finished material Y - BOM
BOM item 1 - material A-qty 8 assign it to routing operation 10
BOM item 2 - material B-qty -5 assign it to routing operation 10
BOM item 2 - material C-qty 10 assign it to routing operation 20
BOM item 3 - material A-qty 2 assign it to routing operation 30
BOM item 4 - material D-qty -2 assign it to routing operation 30
I think this is the only way you can map it.

Netbeans creating wsdl file having message with more than one part...

Hi,
I am using netbeans 6.0.1. I made an xml schema, then I wanted to make an wsdl that uses that schema.
I wanted to put in a message more parts(3), and it would not let me. Then, i made the message with just one part, and added the other parts afterwards.
But now, when I try to make a web service from that wsdl, it says that there is no service in the specified wsdl file.
And if i let that message with just one part, it will make the Web Service.
here is the xml schema and the wsdl file:
XML Schema:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://xml.netbeans.org/schema/Abruf38"
xmlns:tns="http://xml.netbeans.org/schema/Abruf38"
elementFormDefault="qualified">
<xsd:complexType name="FormRequest">
<xsd:sequence>
<xsd:element name="newRequest" type="xsd:boolean"/>
<xsd:element name="requestNumber" type="xsd:int"/>
<xsd:element name="vehicleClass" type="xsd:string"/>
<xsd:element name="vehiclesNumber" type="xsd:int"/>
<xsd:element name="prefferedType" type="xsd:string"/>
<xsd:element name="kombi" type="xsd:boolean"/>
<xsd:element name="usageMission" type="xsd:boolean"/>
<xsd:element name="usageEducation" type="xsd:boolean"/>
<xsd:element name="usageGeneral" type="xsd:boolean"/>
<xsd:element name="usageOthers" type="xsd:string"/>
<xsd:element name="eqVehicle" type="xsd:boolean"/>
<xsd:element name="eqDangerous" type="xsd:boolean"/>
<xsd:element name="eqPlaneSpriegel" type="xsd:boolean"/>
<xsd:element name="eqBegrstll" type="xsd:boolean"/>
<xsd:element name="eqMSitzBTruck" type="xsd:boolean"/>
<xsd:element name="eqVerzurrAusst" type="xsd:boolean"/>
<xsd:element name="eqOthers" type="xsd:string"/>
<xsd:element name="bringService" type="xsd:boolean"/>
<xsd:element name="holService" type="xsd:boolean"/>
<xsd:element name="chauffService" type="xsd:boolean"/>
<xsd:element name="otherService1" type="xsd:string"/>
<xsd:element name="otherService1Chk" type="xsd:boolean"/>
<xsd:element name="otherService2" type="xsd:string"/>
<xsd:element name="otherService2Chk" type="xsd:boolean"/>
<xsd:element name="otherService3" type="xsd:string"/>
<xsd:element name="otherService3Chk" type="xsd:boolean"/>
<xsd:element name="activity" type="xsd:string"/>
<xsd:element name="costPayer" type="xsd:string"/>
<xsd:element name="costCenter" type="xsd:string"/>
<xsd:element name="vehicleCost" type="xsd:float"/>
<xsd:element name="chauffServiceCost" type="xsd:float"/>
<xsd:element name="holBringServiceCost" type="xsd:float"/>
<xsd:element name="totalCost" type="xsd:float"/>
<xsd:element name="tripPurpose" type="xsd:string"/>
<xsd:element name="fixTermin" type="xsd:boolean"/>
<xsd:element name="justificationFix" type="xsd:string"/>
<xsd:element name="requestID" type="xsd:string"/>
<xsd:element name="rentalPeriod" type="tns:RentalPeriod"/>
<xsd:element name="carPool" type="tns:CarPool"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="CarPool">
<xsd:sequence>
<xsd:element name="poolID" type="xsd:string"/>
<xsd:element name="poolName" type="xsd:string"/>
<xsd:element name="orgNumber" type="xsd:string"/>
<xsd:element name="vehicle" maxOccurs="unbounded" type="tns:Vehicle"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="RentalPeriod">
<xsd:sequence>
<xsd:element name="rentalPeriodID" type="xsd:string"/>
<xsd:element name="startDate" type="xsd:date"/>
<xsd:element name="endDate" type="xsd:date"/>
<xsd:element name="startTime" type="xsd:time"/>
<xsd:element name="endTime" type="xsd:time"/>
<xsd:element name="startLocation" type="xsd:string"/>
<xsd:element name="endLocation" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Vehicle">
<xsd:sequence>
<xsd:element name="vehicleID" type="xsd:string"/>
<xsd:element name="vehicleClass" type="xsd:string"/>
<xsd:element name="vehicleRegisterNo" type="xsd:int"/>
<xsd:element name="vehicleType" type="xsd:string"/>
<xsd:element name="seatsNumber" type="xsd:int"/>
<xsd:element name="cost" type="xsd:float"/>
<xsd:element name="available" type="xsd:boolean"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Contact">
<xsd:sequence>
<xsd:element name="contactID" type="xsd:string"/>
<xsd:element name="contactName" type="xsd:string"/>
<xsd:element name="telNumber" type="xsd:int"/>
<xsd:element name="faxNumber" type="xsd:int"/>
<xsd:element name="loNo" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Person">
<xsd:sequence>
<xsd:element name="personID"/>
<xsd:element name="department" type="xsd:string"/>
<xsd:element name="serviceNumber" type="xsd:int"/>
<xsd:element name="contact" type="tns:Contact"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Department">
<xsd:sequence>
<xsd:element name="departmentID" type="xsd:string"/>
<xsd:element name="fundsDepartment" type="xsd:string"/>
<xsd:element name="mvwdst" type="xsd:int"/>
<xsd:element name="distributionNumber" type="xsd:int"/>
<xsd:element name="contact" type="tns:Contact"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="formRequestElement" type="tns:FormRequest"/>
<xsd:element name="personElement" type="tns:Person"/>
<xsd:element name="departmentElement" type="tns:Department"/>
<xsd:element name="vehicle" type="tns:Vehicle"/>
<xsd:element name="loadFormReturn" type="xsd:boolean"/>
<xsd:element name="editFormReturn" type="xsd:boolean"/>
</xsd:schema>
Wsdl File:
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="userWS" targetNamespace="http://j2ee.netbeans.org/wsdl/userWS"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns="http://xml.netbeans.org/schema/Abruf38" xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype" xmlns:tns="http://j2ee.netbeans.org/wsdl/userWS" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types>
<xsd:schema targetNamespace="http://j2ee.netbeans.org/wsdl/userWS">
<xsd:import namespace="http://xml.netbeans.org/schema/Abruf38" schemaLocation="Abruf38.xsd"/>
</xsd:schema>
</types>
<message name="loadFormRequest">
<part name="formRequest" element="ns:formRequestElement"/>
<part name="person" element="ns:personElement"/>
<part name="department" element="ns:departmentElement"/>
</message>
<message name="loadFormReply">
<part name="retVal" element="ns:loadFormReturn"/>
</message>
<portType name="userWSPortType">
<operation name="loadForm">
<input name="input1" message="tns:loadFormRequest"></input>
<output name="output1" message="tns:loadFormReply"/>
</operation>
</portType>
<binding name="userWSBinding" type="tns:userWSPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="loadForm">
<soap:operation/>
<input name="input1">
<soap:body use="literal"/>
</input>
<output name="output1">
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="userWSService">
<port name="userWSPort" binding="tns:userWSBinding">
<soap:address location="http://localhost:18181/userWSService/userWSPort"/>
</port>
</service>
<plnk:partnerLinkType name="userWS1">

<plnk:role name="userWSPortTypeRole" portType="tns:userWSPortType"/>
</plnk:partnerLinkType>
</definitions>
The message that Netbeans says when trying to put more parts to the message is:
WS-I Basic Profile Rule R2210: If a document-literal binding in a DESCRIPTION does not specify the parts attribute on a soapbind:body element, the corresponding abstract wsdl:message MUST define zero or one wsdl:parts.
Please...I am desperate, cause I am pressed by time!
Can anyone tell me how can I make it work. Cause it is very common to use a Web service operation that has more than ONE parameter.
I am waiting for your replys!

Hi,
Change the <soap:binding style="document"... to <soap:binding style="rpc"... and see if that works.
I'm not sure how to get <soap:binding style="document"... working yet - I'm not that experienced in web services yet.
Hope this helps and is not too late.
Regards,
Greg Nye

Nokia messagging: manage more than one account hel...

I'm testing Nokia messaging for a few days
I wonder this:
for now I've set 2 email addresses .. one Alice and one gmail
To read the mail It's enough for me to check only one of the two accounts (everything is forworded to Alice)
But when I respond wuold like to be able to choose from different account
Is there the possibilityto have more than one account (till 10 I know) but make nokia messaging controls only one?
I mean: download only the mail from the email account that I choose ... leave the other account active but with no sync in download
In this way I can download only from one account (faster and no waste of time and space) and be able to answer from different accounts set up in nokia mail site
thanks

Yes you can. If those multiple accounts are for different people, it is usually best for each person to have their own iTunes library in a separate Windows user account.

HT3529 How do I send a text message to more than one phone number at the same time?

How do I send the same text to more than one phone at the same time?

You'll need to see if there's an app in the App Store that does what you want. Search for "Group SMS" or similar.

Web Service with more than one operation?

Hey,
a web service could contain 1..N operations. It is possible
to define this with XI? Normally I took an outbound interface
and create a web service, but this outbound interface defines
the structure of the only operation of this web service, did it?
Does SAP XI supports only a one-operation web service?
thanks
chris

This is supported from PI 7.1 onwards.
VJ

How can I see incoming messages in more than one computer?

I live in two locations, when I open incoming messages on one computer , these messages do not appear on the other computer anymore. There must be an option to see the same messages on the other computer too?

one option is to use [http://en.wikipedia.org/wiki/Internet_Message_Access_Protocol IMAP] . Basically your e-mail will remain on the server of your e-mail provider and you have access to them with TB via IMAP.
Other than that, a second option comes to my mind but it's definately much more complicated, less comfortable and I haven't tried it myself .Try this only if IMAP is NOT an option for you.
You may syncronise the TB E-mail database with some cloud storage provider (like dropbox) on a regular bases.
A good file sync tool is FreeFileSync (Open Source). The problem with this syncing method is that it can't look into e-mails and which side changed/deleted/etc. what. There are various disadvantages here which I can't get into more detail here. Better use IMAP.

Javax.jbi.messaging.MessagingException: More than one operation defined

Similar Messages

Maybe you are looking for