faultstring Cannot find partner wsdl.

Hi ,
I am trying to initiate a web service deployed on a iAS_10g. I have generated a stub, in jdev 10.1.2,from the wsdl end point and am calling the service from the stub.
I am getting the following response:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.generalException</faultcode>
<faultstring>Cannot find partner wsdl.
parnterLink "hello" is not found in process "hello" (revision "1.0")
Please check the deployment descriptor of the process to find the correct partnerLink name.
; nested exception is:
ORABPEL-08021
Cannot find partner wsdl.
parnterLink "hello" is not found in process "hello" (revision "1.0")
Please check the deployment descriptor of the process to find the correct partnerLink name.
</faultstring>
<detail>
<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">m001229</ns1:hostname>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
I have initiated the service and recieved a response successfully, when the same service is deployed on my local server oc4j_10g but not been able to do so for the remote server. Can you please shed some light on this issue?
Thank you for your time.
Regards,
Rev

Hi,
I have the same problem!
Could you please describe what you have done exactly to solve this problem?
Thanks a lot!
Regards,
Piotr

Similar Messages

ORABPEL-08021 Cannot find partner wsdl.

Hi,
From java client I tried to call the "VacationRequest" demo application to initiate new process instance. I got the below error
Note: I can initiate from BPELConsole successfully.
Can you help me out to solve this?
I need to call it using Webservice from differnt m/c in same network. I depolyed simple webservice which I can call from the same client java program.
Regards,
Senthilkumar
==============
Please check the deployment descriptor of the process to find the correct partnerLink name.
] [faultActorURI=null] [DetailEntries=
[(0)=<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">HASSATL-1621765</ns1:
hostname>]
] [FaultEntries=]] [Params={}]
06/01/24 22:44:01 WFAction.java [SOAPException: faultCode=soapenv:Server.generalException; msg=Cannot find partner wsdl.
parnterLink "VacationRequest" is not found in process "VacationRequest" (revision "1.0")
Please check the deployment descriptor of the process to find the correct partnerLink name.
; nested exception is:
ORABPEL-08021
Cannot find partner wsdl.
parnterLink "VacationRequest" is not found in process "VacationRequest" (revision "1.0")
Please check the deployment descriptor of the process to find the correct partnerLink name.
==============

I am getting same error.. here is the snippet from my domain.log
<2006-02-02 10:23:41,487> <DEBUG> <default.collaxa.cube.ws> <CXSOAPProvider::processBPELMessage> url: /default/MainFrameword/1.3/MainFrameword
<2006-02-02 10:23:41,487> <DEBUG> <default.collaxa.cube.ws> <CXSOAPProvider::processBPELMessage> soapAction: /orabpel
<2006-02-02 10:23:41,487> <DEBUG> <default.collaxa.cube.engine.deployment> <CubeProcessHolder::loadAndBind> Check if process MainFrameword, revision 1.3 needs to be reloaded
<2006-02-02 10:23:41,487> <DEBUG> <default.collaxa.cube.ws> <CXSOAPProvider::invoke> Error when process incoming message
ORABPEL-08021
Cannot find partner wsdl.
parnterLink "MainFrameword" is not found in process "MainFrameword" (revision "1.3")
Please check the deployment descriptor of the process to find the correct partnerLink name.
at com.collaxa.cube.ws.wsdl.WSDLManager.getPartnerWSDL(WSDLManager.java:335)
at com.collaxa.cube.ws.wsdl.WSDLManager.getPartnerWSDL(WSDLManager.java:317)
at com.collaxa.cube.ws.soap.providers.CXSOAPProvider.processBPELMessage(CXSOAPProvider.java:193)
at com.collaxa.cube.ws.soap.providers.CXSOAPProvider.invoke(CXSOAPProvider.java:119)
at org.collaxa.thirdparty.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.collaxa.thirdparty.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.collaxa.thirdparty.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.collaxa.thirdparty.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:450)
at org.collaxa.thirdparty.apache.axis.server.AxisServer.invoke(AxisServer.java:285)
at org.collaxa.thirdparty.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:653)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at org.collaxa.thirdparty.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:301)
at com.collaxa.cube.fe.CollaxaServlet.service(CollaxaServlet.java:134)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:798)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:211)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:127)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
<2006-02-02 10:23:41,756> <DEBUG> <default.collaxa.cube.engine.dispatch> <Dispatcher::insert> Received no-op message
<2006-02-02 10:23:41,757> <DEBUG> <default.collaxa.cube.engine.dispatch> <Dispatcher::adjustThreadPool> Allocating 1 thread(s); pending threads: 1, active threads: 0, total: 799
<2006-02-02 10:23:41,757> <DEBUG> <default.collaxa.cube.engine.dispatch> <QueueConnectionPool::getConnection> Fetched a queue connection from pool java:comp/env/jms/collaxa/BPELWorkerQueueFactory, available connections=24, total connections=25
<2006-02-02 10:23:41,758> <DEBUG> <default.collaxa.cube.engine.dispatch> <DispatcherBean::send> Sent message to queue
<2006-02-02 10:23:41,758> <DEBUG> <default.collaxa.cube.engine.dispatch> <QueueConnectionPool::releaseConnection> Released queue connection to pool java:comp/env/jms/collaxa/BPELWorkerQueueFactory, available connections=25, total connections=25
<2006-02-02 10:23:41,759> <DEBUG> <default.collaxa.cube.engine.agents> <SimpleJob::execute> Sent message to dispatcher
<2006-02-02 10:23:41,759> <DEBUG> <default.collaxa.cube.engine.agents> <SimpleScheduler::schedule> Next activation time for agent dispatch: Thu Feb 02 10:25:41 EST 2006

Cannot find the WSDL as I expose a process to web service

Hi,
I have a simple process, and I try to expose it to a web service by using "Process Web Service", and I start the studio web server and test it with "http://localhost:8598/Lesson19-4WebService/webservices/ProcessService?WSDL" but no WSDL appear. Could you help me? Thanks in advance.
Best Regards,
Bill

Please find the following forum.
Process exposed as a web service does not work when deployed
This should resolve the issue.
Hope this helps.
Sarat

Cannot find binding operation definition based on wsaAction='null'

I'm using correlation sets to invoke an axis service asynchronously. I understand that, in this way, passing ws-addressing headers (replyTo, messageId, etc) is not required. However, the generated process' WSDL contains:
<binding name="FlightCallbackPortTypeBinding" type="tns:FlightCallbackPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="flightServiceCallback">
<soap:operation style="document" soapAction="flightServiceCallback"/>
<input>
<soap:header message="tns:WSARelatesToHeader" part="RelatesTo" use="literal" encodingStyle=""/>
<soap:body use="literal"/>
</input>
</operation>
</binding>
When Axis calls back, it sends the message:
POST /orabpel/default/process_wsba/1.0 HTTP/1.0
Content-Type: text/xml; charset=utf-8
User-Agent: Axis/1.3
Host: localhost:8088
SOAPAction: "flightServiceCallback"
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header>
<nsl:RelatesTo soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0" xmlns:nsl="http://schemas.xmlsoap.org/ws/2003/03/addressing">dummyValue</nsl:RelatesTo>
</soapenv:Header>
<soapenv:Body>
<transactionID xsi:type="xsd:string" xmlns="">fe80:0:0:0:207:e9ff:fe44:b4f8:1150081262615 (correlation token)</transactionID>
<price xsi:type="xsd:int" xmlns="">4</price>
</soapenv:Body>
</soapenv:Envelope>
However, I get the error message:
<faultcode>soapenv:Server.generalException</faultcode>
<faultstring>Cannot find binding operation definition based on wsaAction='null', and soapAction='flightServiceCallback' in http://cali:9700/orabpel/default/process_wsba/1.0/_process_wsba.wsdl</faultstring>
<detail>
<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">cali</ns1:hostname>
</detail>
1) What's missing in my callback?
2) Do I need to bother about the wsa header even using correlationSets?
Thank in advance,
Ivan

I have an urgent need for a Sr, Oracle BPEL Developer in the Dallas Texas area. With this position, you can interview and start immediately. If you are interested or know of anyone looking please send my way.
Warm regards,
Kim Dobson
Sr. Account Manager
Eventus Group Technology Resources
10100 N. Central Expressway
Suite 150
Dallas, TX 75231
Office 469.916.4857
Mobile 214.277.2097
Fax 469.916.3861
[email protected]

JAX-WS web service - "Cannot find dispatch method"

I'm getting the same error response every time I send a request to my JAX-WS web service:
<ns2:Fault xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope">
   <faultcode>ns2:Client</faultcode>
   <faultstring>Cannot find dispatch method for {http://www.w3.org/2003/05/soap-envelope}Envelope</faultstring>
</ns2:Fault>I've tried using JAX-WS RI 2.1.7 and 2.2 on my Tomcat server, but both return the same error response. It will return the WSDL just fine (when "?wsdl" is appended to the endpoint URL). I used "wsimport" to generate the necessary Java classes from my WSDL--it used JAX-WS RI 2.1.6 (the one included with the JDK I guess) to generate the Java source files.
Other people online have had similar problems, but never with the SOAP element "{http://www.w3.org/2003/05/soap-envelope}Envelope", always with things specific to their WSDLs like "{}reqParams" or "{http://www.telekom.at/eai/WSToCramerCSIRead}CSIRead". I set a debug breakpoint at the start of my SIB method and it doesn't even get that far.
Any ideas? Thanks for your help.
WSDL:
<?xml version="1.0" encoding="utf-8"?>

<definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ihe="urn:ihe:iti:xds-b:2007" xmlns:iherad="urn:ihe:rad:xdsi-b:2009" xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
targetNamespace="urn:ihe:rad:xdsi-b:2009" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" name="ImagingDocumentSource">
<documentation>IHE XDS-I.b Imaging Document Source</documentation>
<types>
    <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:ihe:iti:xds-b:2007"
      xmlns:ihe="urn:ihe:iti:xds-b:2007">
      
      <xsd:include schemaLocation="../schema/IHE/XDS.b_DocumentRepository.xsd"/>
    </xsd:schema>
    <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:ihe:rad:xdsi-b:2009"
      xmlns:ihe="urn:ihe:iti:xds-b:2007"
      xmlns:iherad="urn:ihe:rad:xdsi-b:2009">
      
      <xsd:include schemaLocation="../schema/IHE/XDSI.b_ImagingDocumentSource.xsd"/>
    </xsd:schema>
    <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
      xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0">
      
      <xsd:include schemaLocation="../schema/ebRS/rs.xsd"/>
    </xsd:schema>
    
    <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0"
      xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0">
      
      <xsd:include schemaLocation="../schema/ebRS/lcm.xsd"/>
    </xsd:schema>
   <xsd:schema elementFormDefault="qualified"
      targetNamespace="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"
      xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0">
      
      <xsd:include schemaLocation="../schema/ebRS/rim.xsd"/>
    </xsd:schema>
</types>
<message name="RetrieveImagingDocumentSetRequest_Message">
    <documentation>Retrieve Imaging Document Set</documentation>
    <part name="body" element="iherad:RetrieveImagingDocumentSetRequest"/>
</message>
<message name="RetrieveDocumentSetResponse_Message">
    <documentation>Retrieve Document Set Response</documentation>
    <part name="body" element="ihe:RetrieveDocumentSetResponse"/>
</message>
<portType name="ImagingDocumentSource_PortType">
    <operation name="ImagingDocumentSource_RetrieveImagingDocumentSet">
      <input message="iherad:RetrieveImagingDocumentSetRequest_Message"
        wsaw:Action="urn:ihe:rad:xdsi-b:2009:RetrieveImagingDocumentSet"/>
      <output message="iherad:RetrieveDocumentSetResponse_Message"
        wsaw:Action="urn:ihe:iti:2007:RetrieveDocumentSetResponse"/>
    </operation>
</portType>
<binding name="ImagingDocumentSource_Binding" type="iherad:ImagingDocumentSource_PortType">
    <soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="ImagingDocumentSource_RetrieveImagingDocumentSet">
      <soap12:operation soapAction="urn:ihe:rad:xdsi-b:2009:RetrieveImagingDocumentSet"/>
      <input>
        <soap12:body use="literal"/>
      </input>
      <output>
        <soap12:body use="literal"/>
      </output>
    </operation>
</binding>
<service name="ImagingDocumentSource_Service">
    <port name="ImagingDocumentSource_Port_Soap12" binding="iherad:ImagingDocumentSource_Binding">
      <soap12:address location="http://localhost:8080/webservice-test/ridsService"/>
    </port>
</service>
</definitions>
Request:
<soap:Envelope
xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:urn="urn:ihe:rad:xdsi-b:2009"
xmlns:urn1="urn:ihe:iti:xds-b:2007"
xmlns:a="http://www.w3.org/2005/08/addressing">
   <soap:Header>
     <a:Action soap:mustUnderstand="1">urn:ihe:rad:2009:RetrieveImagingDocumentSet</a:Action>
     <a:MessageID>urn:uuid:0fbfdced-6c01-4d09-a110-2201afedaa02</a:MessageID>
     <a:ReplyTo soap:mustUnderstand="1">
          <a:Address>http://www.w3.org/2005/08/addressing/anonymous</a:Address>
     </a:ReplyTo>
     <a:To>http://localhost:8080/webservice-test/ridsServer</a:To>
   </soap:Header>
   <soap:Body>
      <urn:RetrieveImagingDocumentSetRequest>
         
         <urn:StudyRequest studyInstanceUID="test1">
            
            <urn:SeriesRequest seriesInstanceUID="test2">
               
               <urn1:DocumentRequest>
                  
                  <urn1:HomeCommunityId>test3</urn1:HomeCommunityId>
                  <urn1:RepositoryUniqueId>test4</urn1:RepositoryUniqueId>
                  <urn1:DocumentUniqueId>test5</urn1:DocumentUniqueId>
               </urn1:DocumentRequest>
            </urn:SeriesRequest>
         </urn:StudyRequest>
         <urn:TransferSyntaxUIDList>
            
            <urn:TransferSyntaxUID>?</urn:TransferSyntaxUID>
         </urn:TransferSyntaxUIDList>
      </urn:RetrieveImagingDocumentSetRequest>
   </soap:Body>
</soap:Envelope>
Response (HTTP 500):
<ns2:Fault xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope">
   <faultcode>ns2:Client</faultcode>
   <faultstring>Cannot find dispatch method for {http://www.w3.org/2003/05/soap-envelope}Envelope</faultstring>
</ns2:Fault>

I posted here to benefit anybody who is looking for a solution.
The solution is to use WebServiceContext to get ServletContext, then use ServletContext to get parameters defined in web.xml.
@Resource private WebServiceContext m_wsCxt;
Then in method
SOAPMessageContext soapCxt = (SOAPMessageContext) m_wsCxt.getMessageContext();
ServletContext servletCxt = (ServletContext) soapCxt.get(javax.xml.ws.handler.MessageContext.SERVLET_CONTEXT);
}

Weird soap issue: Cannot find the dispatch method

Hi,
I'm having strange problem with SOAP message.
I created a simple web service using jax-ws, wsgen, and so on. I deployed it on sun app server 9.0. I wrote client application (i'm using SAAJ 1.3) for testing. The response I'm getting is something like this:
<soapenv:Envelope xmlns:ns1="http://put/"
   xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <soapenv:Body>
      <soapenv:Fault>
         <faultcode>soapenv:Client</faultcode>
         <faultstring>Cannot find the dispatch method</faultstring>
      </soapenv:Fault>
   </soapenv:Body>
</soapenv:Envelope>First I thought there's a problem with webservice I created. So I downloaded soapui (www.soapui.org) for testing. I provided it with wsdl and endpoint. And web sevice seems to work corectly - response I got back was ok.
The strange part is: soap messages sent from soapui and from client application written by me seem to be identical. Both look like this:
<SOAP-ENV:Envelope
   xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:put="http://put">
   <SOAP-ENV:Body>
      <put:sayHello>
         <arg0>test</arg0>
      </put:sayHello>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>I even sniffed packets (WinDump) sent to application server and in both cases soap message is the same. There's only a slight difference in http headers. Here's what server log contains after receiving a soap message from my client application:
DetailsTimestamp:     2006-09-14 13:28:03.315
Log Level:      SEVERE
Logger:     javax.enterprise.resource.webservices.jaxws.server.soapmd
Name-Value Pairs:     _ThreadID=13;
Record Number:     443
Message ID:     Error in decoding SOAP Message Error in decoding SOAP Message at com.sun.xml.ws.encoding.
soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java
Complete Message
86)
     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.
toMessageInfo(SOAPMessageDispatcher.java:168)
     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher$SoapInvoker.
invoke(SOAPMessageDispatcher.java:533)
     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:144)
     at com.sun.xml.ws.server.Tie.handle(Tie.java:88)
     at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.handle(WSServletDelegate.java:279)
     at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:232)
     at com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java:77)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:767)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
     at sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:257)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:132)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:189)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.doProcess(ProcessorTask.java:604)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:475)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:371)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:264)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:281)
     at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:83)
Caused by: javax.xml.ws.soap.SOAPFaultException: Cannot find the dispatch method
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.raiseFault(SOAPDecoder.java:662)
     at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.decodeDispatchMethod(SOAPXMLDecoder.java:151)
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBodyContent(SOAPDecoder.java:335)
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBody(SOAPDecoder.java:325)
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeEnvelope(SOAPDecoder.java:248)
     at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java:78)
     ... 39 moreI'm new to web services and I'm completely out of ideas what is the problem. I googled a lot but I can't find any solution. Any help would be appreciated :)
null

Are you saying I can't just write jax-ws based web service using @WebService and @WebMethod and then, on client side, write code like this?
SOAPConnectionFactory soapConnectionFactory = SOAPConnectionFactory.newInstance();
SOAPConnection connection = soapConnectionFactory.createConnection();
MessageFactory factory = MessageFactory.newInstance(SOAPConstants.SOAP_1_1_PROTOCOL);
SOAPMessage request = factory.createMessage();
// create proper message elements
URL endpoint = new URL(endpoint_url);
SOAPMessage response = connection.call(request, endpoint);
// process response
//

Soap fault, cannot find the dispatch method

I deploy the HelloService example from "The Java EE 5 Tutorial
For Sun Java System Application Server Platform Edition 9, chapter 1" to Sun Java System Application Server Platform Edition 9.0 Beta (build b32g), I tested it and it works find but when I invoked it from Servicemix-3.0 which use org.apache.servicemix.components.saaj.SaajBinding i got the following response:
<?xml version="1.0" ?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://endpoint.helloservice/"><soapenv:Body><soapenv:Fault xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>soapenv:Client</faultcode><faultstring>Cannot find the dispatch method</faultstring></soapenv:Fault></soapenv:Body></soapenv:Envelope>
Using the Monitor to look at the request message I could not see any significant difference, follows both requests:
Test:
<?xml version="1.0" ?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://endpoint.helloservice/"><soapenv:Body><ns1:sayHello><arg0>ffg</arg0></ns1:sayHello></soapenv:Body></soapenv:Envelope>
servicemix:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><SOAP-ENV:Envelope xmlns:ns1="http://endpoint.helloservice/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Body> <ns1:sayHello> <arg0>Leopoldo</arg0> </ns1:sayHello> </SOAP-ENV:Body> </SOAP-ENV:Envelope></SOAP-ENV:Body></SOAP-ENV:Envelope>
The log entry detail asociate is:
Message ID: Error in decoding SOAP Message Error in decoding SOAP Message at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java
Complete Message
86)     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.toMessageInfo(SOAPMessageDispatcher.java:168)     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher$SoapInvoker.invoke(SOAPMessageDispatcher.java:533)     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:144)     at com.sun.xml.ws.server.Tie.handle(Tie.java:88)     at com.sun.enterprise.webservice.JAXWSServlet.doPost(JAXWSServlet.java:174)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:822)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)     at java.lang.reflect.Method.invoke(Method.java:585)     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:262)     at java.security.AccessController.doPrivileged(Native Method)     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:295)     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:178)     at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:390)     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:279)     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)     at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:174)     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)     at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:223)     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:664)     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:571)     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:846)     at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:345)     at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:237)     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:240)     at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)Caused by: javax.xml.ws.soap.SOAPFaultException: Cannot find the dispatch method     at com.sun.xml.ws.encoding.soap.SOAPDecoder.raiseFault(SOAPDecoder.java:662)     at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.decodeDispatchMethod(SOAPXMLDecoder.java:151)     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBodyContent(SOAPDecoder.java:335)     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBody(SOAPDecoder.java:325)     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeEnvelope(SOAPDecoder.java:248)     at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java:78)     ... 40 more
I shall appreciate any help on this issue

Any luck? I'm having the same problem with the HelloService deployed on AS9. The service tests ok and the client code in the jwsdk2.0 runs ok. When I attempt to access the service using axis 1.4, the same error occurs. I'll keep working on it, and post a solution if/when this is resolved.
Client code:
* Copyright 2001-2004 The Apache Software Foundation.
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*      http://www.apache.org/licenses/LICENSE-2.0
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
import org.apache.axis.client.Call;
import org.apache.axis.client.Service;
import javax.xml.namespace.QName;
public class TestClient
   public static void main(String [] args) {
       try {
           String endpoint =
                    "http://localhost:9090/helloservice/HelloService";
           Service service = new Service();
           Call     call    = (Call) service.createCall();
           call.setTargetEndpointAddress( new java.net.URL(endpoint) );
           call.setOperationName(new QName("http://soapinterop.org/", "sayHello") );
           // Call to addParameter/setReturnType as described in user-guide.html
           //call.addParameter("testParam",
           //                  org.apache.axis.Constants.XSD_STRING,
           //                  javax.xml.rpc.ParameterMode.IN);
           //call.setReturnType(org.apache.axis.Constants.XSD_STRING);
           String ret = (String) call.invoke( new Object[] { "Hello!" } );
           System.out.println("Sent 'Hello!', got '" + ret + "'");
       } catch (Exception e) {
           e.printStackTrace();
}Error in decoding SOAP Message Error in decoding SOAP Message at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java
89)
     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.toMessageInfo(SOAPMessageDispatcher.java:187)
     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher$SoapInvoker.invoke(SOAPMessageDispatcher.java:571)
     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:145)
     at com.sun.xml.ws.server.Tie.handle(Tie.java:88)
     at com.sun.enterprise.webservice.JAXWSServlet.doPost(JAXWSServlet.java:191)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:231)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
     at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
Caused by: javax.xml.ws.soap.SOAPFaultException: Cannot find the dispatch method
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.raiseFault(SOAPDecoder.java:674)
     at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.decodeDispatchMethod(SOAPXMLDecoder.java:152)
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBodyContent(SOAPDecoder.java:337)
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBody(SOAPDecoder.java:327)
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeEnvelope(SOAPDecoder.java:250)
     at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java:81)
     ... 31 more
Mesage:
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:sayHello soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://soapinterop.org/"><ns1:arg0 xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">Hello!</ns1:arg0></ns1:sayHello></soapenv:Body></soapenv:Envelope>

I cannot find my partner portal

I have not logged in for months.
I try to log in then it forced a password reset - ok I did that then it would not accept me new password so I reset the password again. Then it worked !!!
When I login to the partner portal url, using the login link at the top right of http://businesscatalyst.com/partners then I end up in the admin for one site (my free partner site) but no links anywhere to a partner portal - I wanting to see my list of customer sites and what they are paying etc.
How come i can no longer get into the partner portal? And how do I get to it?
How come I have to add a forum question to get support? Sorry we have normal web hosting for most of our sites and I can phone or live chat with a person anytime. BC mentioned somewhere there is live chat - I looked and looked but cannot find it

Hi
Thanks. No menu when I hover over the logo.
As i said my user/pass worked before (could access portal) when i logged in months ago - Its not changed and I have only ever has one user/pass
Then when i try today it FORCED a password change NOW I cannot get into the portal.I only have access to the free partner site alerto24.com/admin
Please can someone from Adobe fix this and email me at [email protected] asap
Thanks
Paul

Getting Error- Desktop\WSDL1\main.wsdl The system cannot find the path spec

Hai to every one !
iam using wsdl file which is downloaded "wsdlzip" file from wsnavigator to my desktop.
Extracted zip file .
i used main.wsdl file as adaptive webservice model in webdynpro application.
I developed application then iam not getting output , facing error like
java.io.FileNotFoundException: Desktop\WSDL1\main.wsdl (The system cannot find the path specified)
could any body help me on this.

Hi Eswar,
While importing WSDL using Adaptiver WS did you use the WS destinations. If yes, then did you create WS Destinations in the Visual Administrator?
You need to provide the url of the webservice in WSDestinations in Visual Administrator. It should be the url of the webservice in which the webservice is deployed and not the desktop URL.
the url will be like this
Ex: http://host:50000/OrderRequestForEBasis/Config1?wsdl
This url you can get by going to
http://host:port/wsnavigator in which server your webservice is located.
Thanks,
Gopi

Log_policy in OSB - Cannot find policies in WSDL

Hi,
I attached oracle/log_policy to a proxy service in OSB. When I clicked on debug icon to run the test the popup window display this error:
oracle.wsm.policymanager.PolicyManagerException: WSM-02133 : Cannot find policies in WSDL. [Possible Cause : WSM-02133 : Cannot find policies in WSDL.]
When I created the OSB domain, I refered to the MDS schema correctly.
Any help will be appreciated.

Hi,
I have applied oracle/wss_username_token_service_policy for my proxy service and trying to test that from OSB Test Console. I am getting below error,
"[OSB Security - OWSM:387253]Failed to initialize Owsm Credential Manager. Please validate the Keystore Configuration"
When i have launched Test Console for this proxy, i have observed in Security part, oracle/wss_username_token_client_policy is appearing. I am not sure why oracle/wss_username_token_client_policy is appearing there when i applied oracle/wss_username_token_service_policy to my proxy service.
Also do i have to need to configure any Keystore for oracle/wss_username_token_service_policy, If so please tell me the process.
If no key store is required where will the credentials be stored.
Also can you help in solving the error *"[OSB Security - OWSM:387253]Failed to initialize Owsm Credential Manager. Please validate the Keystore Configuration"*
Thanks
Rajesh

Cannot find entry 'SOAP_DOC_LITERAL' when import PublicReportService wsdl

Hi,
when i when import PublicReportService_v11.wsdl from BIP 10.1.3.4.2, i get the following error msg:
Cannot find entry 'SOAP_DOC_LITERAL' in the bounded picklist for the field 'Protocol' in integration component 'Repository Port'(SBL-EAI-
04401)
I want to integrate BI publisher for Siebel 8.1.1.6 to generate a report.
I followed the following references:
http://docs.oracle.com/cd/E14004_01/books/Reports/ReportsIntegrate6.html#wp575974
http://siebel-essentials.blogspot.com/2010/01/siebel-811x-and-bi-publisher-part-1.html#axzz1vaWerxQa
Thanks

Hi, WSeibel
I followed the steps Doc ID 1076412.1,
it said
This problem was solved after defining in the Mobile Client view -> field "Language(s)" the language ENU and the other one being used.
Then the database was re-extracted and it was possible to import the WSDL in the local database using Tools.
but my issue is not solved well.
I decide to reinstall Siebel Tools now, and have a try again.
Thanks,
Zhaoqiang

Error cvc-elt.1: Cannot find the declaration of element 'wsdl:definitions'

Hi! Ive got an error: cvc-elt.1: Cannot find the declaration of element 'wsdl:definitions'
My WSDL file was generated by PI.
After import this WSDL-file to my Business Process to section Service Interfaces - I've got this error.
But, it seems to be OK when I created the project, create a model by choosing the WSDL-file. All validators do not give me any error.
Whats wrong?!

Though this is not my area, you can have a look at this thread which may help you
[Re: XML inputs in a MII transaction to be used as a Web Service call|XML inputs in a MII transaction to be used as a Web Service call;
thanks
G. Lakshmipathi

Pi 7.1: Exception when contacting WS - "Cannot find dispatch method"

Hi All,
I have been receiving the following error message as shown in ICM log, where the trace level is set to 3, when a request is sent to a Web Server.
...<SOAP:Faultmlns:SOAP='htt//schemas.xmlsp.org/soap/envope/'><faultco>SOAP:Client</ultcode><faultring>Cannot find dispatch method for arg0</faultstring/SOAP:Fault>..
No error message is returned using a soap client (as soapUI), after loading the same wsdl file.
About the configuration of the SOAP Communication Channel, no conversion parameter have been set and no SOAP Action has been set because the seme exception is also raised by setting "arg0" as SOAP Action.
The structure of the response message is like this.
<Field1>
   <arg0>
       <field2>
       <field3>
Any help will be well appreciated.
Many thanks in advacne for your kind support.
Regards,
       Giovanni

Hi All !!
This problem has been solved with the last SAP_XI* Patches.
We install:
SAP_XIESR SP06 Patch 11
SAP_XIAF   SP06 Patch 11
SAP_XITOOL SP06 Patch 10
and the problem...... SOLVED !!!
Regards,
Juan.

Cannot find the field for the Contact Role in Contact object.

Hi, friends,
I need to set Contact Role when creating new Account and Contact. I tried the following tests but cannot figure it out:
1. Create new Account and then new Contact, set the AccountContactRole in Account WSDL as “Main” but failed to set that field in form
2. Create new Account and then new Contact, set the ContactRole in Contact WSDL as "Main” but failed to set that field in form
3. Create new Contact and then new Account, set those two fields, but failed to set that field in form
So far I know, the Account Contact Role is kind of picklist type in Account Contact Field. I could find its customization in Admin-> Application Customization -> Account -> Account Contact Fields -> Contact Roles. However, I cannot find the exact item in WSDL file to map this item. The AccountContactRole in Account WSDL and ContactRole in Contact WSDL are suspicious.
It will be appreciated if anyone could help me on this issue.
Thank you very much
Ray
Edited by: user9015675 on Jan 19, 2010 2:59 PM

Hi, Sean, I tried the Web Service 1.0 call to create a new Contact and then a new Account with created Contact ID. But the CRMOD return the "Access Deny" fault. Is there somewhere I could see or change this kind of access rights? Or some bug in my web service call?
I am sorry I did not open a new topic thread as I think they are related and easy for reference. Thank you very much.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<AccountWS_AccountInsert_Input xmlns="urn:crmondemand/ws/account/10/2004" xmlns:ns2="urn:/crmondemand/xml/account">
<ns2:ListOfAccount>
<ns2:Account>
<ns2:AccountName>XXXX1264030832268</ns2:AccountName>
<ns2:ListOfContactRole>
<ns2:ContactRole>
<ns2:ContactRole>Main</ns2:ContactRole>
<ns2:ContactId>XXXX1264030828034</ns2:ContactId>
</ns2:ContactRole>
</ns2:ListOfContactRole>
</ns2:Account>
</ns2:ListOfAccount>
</AccountWS_AccountInsert_Input>
</soap:Body>
</soap:Envelope>
Return:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>Method 'SetFieldValue' of business component 'Account Contact Role' (integration component 'Account Contact Role') returned the following error:
"Access denied.(SBL-DAT-00542)"(SBL-EAI-04376)</faultstring>
<detail>
<siebelf:siebdetail xmlns:siebelf="http://www.siebel.com/ws/fault">
<siebelf:logfilename>OnDemandServicesObjMgr_enu_18122.log</siebelf:logfilename>
<siebelf:errorstack>
<siebelf:error>
<siebelf:errorcode>(SBL-DAT-00542)</siebelf:errorcode>
<siebelf:errorsymbol></siebelf:errorsymbol>
<siebelf:errormsg>Method 'SetFieldValue' of business component 'Account Contact Role' (integration component 'Account Contact Role') returned the following error:
"Access denied.(SBL-DAT-00542)"(SBL-EAI-04376)</siebelf:errormsg>
</siebelf:error>
</siebelf:errorstack>
</siebelf:siebdetail>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

BPEL Correlation: ORABPEL-03812 Cannot find property alias.

HI,
I have created a BPEL process, that places a message into a JMS queue, and waits to receive a response in anoter JMS queue.
In both the request and response message types, there is a uuid field, that has been populated initially with generateGUID() function etc.
I plan to correlate based on this value.
I am using correlation sets to correlated to the BPEL instance using the uuid field in the request and response fields.
Ive gone by the book i.e. BPEL developer guide, in creating the Correlation set, property, property aliases etc.
I am able to successfully compile and deploy the process.
But on execution of the BPEL instance i get error as follows.
<default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "cube delivery": Cannot find property alias.
Cannot find the property alias "{http://pli.techm.com/JMSAsyncSyncProcess/correlationset}jms_uuid", message type "".
Please check your BPEL/WSDL source to make sure that property alias "{http://pli.techm.com/JMSAsyncSyncProcess/correlationset}jms_uuid" has been defined.
ORABPEL-03812
Cannot find property alias.
Cannot find the property alias "{http://pli.techm.com/JMSAsyncSyncProcess/correlationset}jms_uuid", message type "".
Please check your BPEL/WSDL source to make sure that property alias "{http://pli.techm.com/JMSAsyncSyncProcess/correlationset}jms_uuid" has been defined.
Due to this the BPEL process instance itself is not created and thus no further action can be taken.
Ive ensured that all necessary imports into the various wsdl files (including partner wsdl files) are present.
Can somebody please help?

Hi,
I solved the problem too :)
In the outbound jms adapter call, where the correlation is be started, there is an in|out|in-out attribute that needs to be set to out. probabaly signifies the outbound message from that node.
This worked :)
let me know if you tried something else...

faultstring Cannot find partner wsdl.

Similar Messages

Maybe you are looking for