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.

Similar Messages

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

HT1349 I am trying to burn music to a CD - message says: unable to locate the original file and will not burn the playlist. Is there a setting that I must change. ?

I am trying to burn music to a CD-R- message says: unable to locate the original file. Music is on the iTunes program but will not play or burn. Is there something I should change to be able to burn to CD?

If they were songs you purchased from itunes, try redownloading them from your purchases...
if that doednt work, make sure the optuon to copy files to itunes media folder is checked in settings, then find and download from the net. and re-add them to your library

Messaging Server 4: WebMail login returns "unable to locate the server"

When I log into WebMail, the following error occurs: 

Netscape is unable to locate the server hostname.
Please check the server name and try again.

End User

First verify that you cannot reach the hostname
server by using the ping
utility (Windows NT or Unix). If
you cannot reach the host, report this problem to the appropriate system
administrator or help desk.

However, if you can reach the host with ping
, then the problem may be a minor
networking issue that you can resolve. There is also the possibility that
the network has been configured to allow users to ping
unreachable systems. You can use the
following actions to rule out possible sources of the problem: 

<OL>
<LI>Attempt to log in to WebMail again. If you can log in successfully, then
the problem with the WebMail server may have been temporary or is an
intermittent problem.

<LI>End the current browser session and then restart the browser and try to
connect to the WebMail server again. If you can log in successfully, then,
most likely, the browser had cached some old network information that was
reset when you exited the browser.

<LI>Verify the DNS configuration of your system and then restart the entire
system.
</OL>

If the above actions do not work, then you will need to contact the
system administrator or the help desk.

Mail Server Administrators

As the problem with connecting to the WebMail server is caused by configuration
or availability problems, make sure that users who report this problem have
HTTP network connectivity to the hostname. The following scenarios are
possible causes of connectivity problems: 

<UL>
<LI>Users have the wrong proxy.
<LI>Users are being blocked by firewalls.
<LI>Users are connecting from the wrong network.
<LI>Users specify the incorrect DNS servers.
</UL>

In addition, users may also report that the server is down. As the login page
for WebMail does not contain URL links that are FQDNs or absolute path names,
it is possible that users may still be able to see the login window if it was
cached or loaded before the server stopped working.

In some cases, it may be necessary to access the hostname that is used in the
WebMail links. This hostname setting is stored in the configdb
parameter
service.smtp.messagehostname.
This configuration setting is not mentioned in the Messaging Server
documentation.

The messagehostname is a
configuration value that affects many server functions. For this reason, do
not make changes to this value without first considering the effects of such a
change on other WebMail settings, such as the postmaster group and user
mailhost values. Also, please note that changing messagehostname
is not supported from Console.

For more information on messagehostname
, please see "What is messagehostname?"
at 
article 4250

You can also find documentation for configutil
in the Messaging Server Administrator's
Guide at the following URL: 

http://docs.iplanet.com/docs/manuals/messaging/nms41/ag/cmdline.htm#1003887

Note: You must stop and restart the HTTP service in order for changes to
the messagehostname to
take effect.

When I log into WebMail, the following error occurs: 

Netscape is unable to locate the server hostname.
Please check the server name and try again.

End User

First verify that you cannot reach the hostname
server by using the ping
utility (Windows NT or Unix). If
you cannot reach the host, report this problem to the appropriate system
administrator or help desk.

However, if you can reach the host with ping
, then the problem may be a minor
networking issue that you can resolve. There is also the possibility that
the network has been configured to allow users to ping
unreachable systems. You can use the
following actions to rule out possible sources of the problem: 

<OL>
<LI>Attempt to log in to WebMail again. If you can log in successfully, then
the problem with the WebMail server may have been temporary or is an
intermittent problem.

<LI>End the current browser session and then restart the browser and try to
connect to the WebMail server again. If you can log in successfully, then,
most likely, the browser had cached some old network information that was
reset when you exited the browser.

<LI>Verify the DNS configuration of your system and then restart the entire
system.
</OL>

If the above actions do not work, then you will need to contact the
system administrator or the help desk.

Mail Server Administrators

As the problem with connecting to the WebMail server is caused by configuration
or availability problems, make sure that users who report this problem have
HTTP network connectivity to the hostname. The following scenarios are
possible causes of connectivity problems: 

<UL>
<LI>Users have the wrong proxy.
<LI>Users are being blocked by firewalls.
<LI>Users are connecting from the wrong network.
<LI>Users specify the incorrect DNS servers.
</UL>

In addition, users may also report that the server is down. As the login page
for WebMail does not contain URL links that are FQDNs or absolute path names,
it is possible that users may still be able to see the login window if it was
cached or loaded before the server stopped working.

In some cases, it may be necessary to access the hostname that is used in the
WebMail links. This hostname setting is stored in the configdb
parameter
service.smtp.messagehostname.
This configuration setting is not mentioned in the Messaging Server
documentation.

The messagehostname is a
configuration value that affects many server functions. For this reason, do
not make changes to this value without first considering the effects of such a
change on other WebMail settings, such as the postmaster group and user
mailhost values. Also, please note that changing messagehostname
is not supported from Console.

For more information on messagehostname
, please see "What is messagehostname?"
at 
article 4250

You can also find documentation for configutil
in the Messaging Server Administrator's
Guide at the following URL: 

http://docs.iplanet.com/docs/manuals/messaging/nms41/ag/cmdline.htm#1003887

Note: You must stop and restart the HTTP service in order for changes to
the messagehostname to
take effect.

I use a macbook pro. Several months ago I signed up for the Photoshop/lightroom offer and the payments are taken from my bank but I am unable to locate the product. I just get a message saying that my trial is expired. I am really desperate.

I use a macbook pro. Several months ago I signed up for the Photoshop/lightroom offer and the payments are taken from my bank but I am unable to locate the product. I just get a message saying that my trial is expired. I am really desperate.

Sign in, activation, or connection errors | CS5.5 and later
Mylenium

Real time transaction response - unable to locate the root element

Hi There
Has anyone integrated webMethods with Data Services 3.2 for real time transactions?
We are trying to create a real time dataflow, initiated by webMethods. We are sending the request to the Access Server which runs our
real time dataflow and does process the request. However, our return response is null. No data in the response back to webMethods. We have
tested this in soapUI, and our transaction does work. We get the correct response back.
So my question is has any experienced this issue with webMethods? Any suggestions or ideas?
Here is the error
===========================================
Path name:
     PortType: Real-time_Services
     Operation: Realtime_address_cleanse
WSDL code: S-9043
[ISS.0092.9043] Schema Error: 1
     pathName: null
     errorCode: CONV-004
     errorMessage: [ISC.0082.9104] DataOut - unable to locate the root element
     identifier: null
===========================================
ps- xmlspy does not work as well
Please let me know
Thanks
Kurt

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.

DVR Message: Error: Unable to play the selected program. Please try again later.

I just watched a recorded show in a series from my DVR (located in the living room) fine in my bedroom (non-DVR). When I went to watch the next show, I get this error: "DVR Message: Error: Unable to play the selected program. Please try again later."
However, if I go into my living room and try to watch that show from my DVR, I can watch it.
Any suggestions on what is happening?

Hi there, I am very sorry about the trouble you are having with your DVR playback. Here are a few things that you can try to get this issue resolved. First try to unplug the DVR from the power for a full minute and restore power to the unit. If that does not work try unplugging the power from your FIOS router for 30 seconds and restore power to the unit. The light that is critical is the Coax LAN light if that light is not lit the DVR will not be able to communicate with the other set-top boxes.
Hope this helps!
--James
--James
Verizon Support
Notice: Content posted by Verizon employees is meant to be informational and does not supersede or change the Verizon Forums User Guidelines or Terms or Service, or your Customer Agreement Terms and Conditions or Plan.

Problems installing 8.0.2 update (unable to locate the product)

Hello, I'm trying to install the patch 8.0.2 for AAE CS3 on WinXP(32bit) SP3, but I'm getting a message "The updater is unable to locate the product to be updated.". Can I do something with that?

Yepp, as Jonas said, give them a call. On a guess I would assume that you installed to a non-standard path or another Adobe product has messed up the pertinent install info, but you never know, so it's best to contact phone support and explain the situation and steps taken so far.
Mylenium

Javax.xml.bind.JAXBException: Unable to locate jaxb.properties for package ...

I want to marshall a java content tree (generated with jaxb api) in xml stream
in an EJB.
Generated classes are archived in a jar file containing its jaxb.properties, when
I test it
in a classic java process it runs well.
When I try to do it in an EJB with weblogic 8.1 I get the following error:
javax.xml.bind.JAXBException: Unable to locate jaxb.properties for package
I've checked:
- jaxb.properties is in the archive file
I've tried to put the jar file in the classpath of the server in the starter script.
I've tried to put reference classpath in the manifest of the ejb jar and of application
ear.
I've tried to put both reference in server classpath and ear/jar manifest.
I still doesn't run.
Any idea?
Thanks a lot
Franck

Add the directory of the generated classes in the classpath.
"franck" <[email protected]> wrote:
>
I want to marshall a java content tree (generated with jaxb api) in xml
stream
in an EJB.
Generated classes are archived in a jar file containing its jaxb.properties,
when
I test it
in a classic java process it runs well.
When I try to do it in an EJB with weblogic 8.1 I get the following error:
javax.xml.bind.JAXBException: Unable to locate jaxb.properties for package
I've checked:
- jaxb.properties is in the archive file
I've tried to put the jar file in the classpath of the server in the
starter script.
I've tried to put reference classpath in the manifest of the ejb jar
and of application
ear.
I've tried to put both reference in server classpath and ear/jar manifest.
I still doesn't run.
Any idea?
Thanks a lot
Franck

Upon Preview View: "Unable to locate the file."

When clicking on the Preview View icon with an ebook selected in the View pane, I get the error message "Unable to locate the file. This item has been moved, renamed or deleted". This happened after I created collections, and dragged books from the Library into the collections.

The link below will provide the information needed to resolve the current Sony Reader issue you are experiencing.
http://www.kb.sony.com/selfservice/micr ... 0203266040

Unable to locate the xml-definition for FieldName with FieldId '1f8a351c-965d-4927-9c22-8772b7089f55' when trying to activate feature with references a custom field type

I´ve a solution which contains a custom field type (found somewhere on the net, the custom field type maps a choice field to managed metadata). There is a second solution which contains site column and site content type definitions using the custom field
type definition from field type solution.
On my developement environment, there is no problem with this two solutions. When field type solution is deployed, i can deploy the content type solution and activate the feature and everything is fine.
However if i give the two solutions to our adminstrator to deploy them into our staging environment, content type feature activation fails. Deploying the field type solution makes no problems. The field type is then available and i can manually creates
columns with this new field type. However activating the content type solution fails with the error shown in the title of this message. The FieldID from the message is not part of my content type project. Searching the net doens´t show any results for that
id. So i think it´s not some of the standard field id´s from sharepoint.
Can anyone help?

Stack Trace
Unable to locate the xml-definition for FieldName with FieldId '1f8a351c-965d-4927-9c22-8772b7089f55', exception: Microsoft.SharePoint.SPException: Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED)) ---> System.Runtime.InteropServices.COMException (0x8000FFFF): Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))
at Microsoft.SharePoint.Library.SPRequestInternalClass.GetGlobalContentTypeXml(String bstrUrl, Int32 type, UInt32 lcid, Object varIdBytes)
at Microsoft.SharePoint.Library.SPRequest.GetGlobalContentTypeXml(String bstrUrl, Int32 type, UInt32 lcid, Object varIdBytes) -
-- End of inner exception stack trace ---
at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
at Microsoft.SharePoint.Library.SPRequest.GetGlobalContentTypeXml(String bstrUrl, Int32 type, UInt32 lcid, Object varIdBytes)
at Microsoft.SharePoint.SPFieldCollection.FetchFieldsFromWeb()

UNABLE TO LOCATE THE THE LABVIEW RUN-TIME ENGINE.LVBROKERAUX71

UNABLE TO LOCATE THE THE LABVIEW RUN-TIME ENGINE.LVBROKERAUX71 REQUIRES A VERSION 7.1 (OR COMPATIBLE) LABVIEW RUN-TIME ENGINE。PLEASE CONTACT THE VENDOR OF LVBROKERAUX71 TO CORRECT THIS PROBLEM
Uninstalled DAQ and reinstalled. MAX still throws an error.
Any Isead besides uninstalling 3/4 of my software?
Merry Christmas!
Matthew Fitzsimons
Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

To clean up your system, you will need to uninstall the LabVIEW 7.1 run-time engine, and the "LVBroker," and the "LVBrokerAux71" components using the MSI Blast utility. To obtain this utility, please create a service request for phone or e-mail support, and contact one of our Applications Engineers about this issue. Thank you!

In Printer Services box, i get the message "unable to perform the operation"

HP Officejet H470wbt. Using via bluetooth. i have recently installed a new ink service module and a black toner cartridge. Now I get the following message when trying to view ink levels in the printer services area--"unable to perform the operation"

"Clear the Cache": Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now" 
"Remove the Cookies" from sites that cause problems: Tools > Options > Privacy > Cookies: "Show Cookies" 
 
Start Firefox in [[Safe Mode]] to check if one of your add-ons is causing your problem (switch to the DEFAULT theme: Tools > Add-ons > Themes). 
See [[Troubleshooting extensions and themes]] and [[Troubleshooting plugins]]

Unable to locate the LMS's API Implementation-Error in Content Player

Dear Guys,
when I am playing the content in content player of Authering environment we get the following error "Unable to locate the LMS's API Implementation" ,
Should any API be implemented explicitly?
How can we resolve this error?
Regards,
Shamila.

Hi Shamila!
As I mentioned, you need to consult your content developer to debug this issue. In the course content(i.e. flash file) there are references to the SCORM API. These when imported in to AE loose the reference. For instance, if you have something like this .. parent.api.<some scrom function> and the parent (window or frame) has the SCORM API. This reference might be getting broken when the course package is imported in to AE. The content developer need to make changes in the code to ensure the reference to the API is changed.
Please let me know if you require further guidance on this.
Regards,
Ravi Sekhar

Error when opening: "DiscoBrick 1.60. Unable to locate the plugin. Repair permissions and retry."

Error when opening: "DiscoBrick 1.60. Unable to locate the <> plugin. Repair permissions and retry."

I also got this error this morning. DiscoBrick is just a visual plug-in for itunes that i don't even use, so i just uninstalled it and that solved my problem.
Go to MacHD/Library/iTunes/iTunes Plug Ins/ then delete DiscoBrick.
If you still want it you could try re-installing it again
Glen.

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

Similar Messages

Maybe you are looking for