<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode xmlns="">env:Server</faultcode>
<faultstring xmlns="">ORABPEL-08021 Cannot find partner wsdl. parnterLink "MyService" is not found in process "MyService" (revision "1.0") Please check the deployment descriptor of the process to find the correct partnerLink name.
</faultstring>
<faultactor xmlns=""></faultactor>
</env:Fault>
</env:Body>
</env:Envelope>
The problem was that I was using the wrong URI to access the service. I was using:
http://myserver:8888/orabpel/default/MyService/1.0/MyService
and I should have been using:
http://myserver:8888/orabpel/default/MyService/1.0
So, my own silly fault really! Normally I can take the WSDL address (eg. http://myserver:8888/orabpel/default/MyService/1.0/MyService?wsdl) and just drop the "?wsdl" off the end to get the service endpoint. Not with these Oracle BPEL services though. If I had bothered to read the WSDL, I would have seen that the endpoint address is clearly specified. One more thing to note: with an Oracle BPEL service, you can also drop the version number off the end and it will still work, calling the latest version by default. eg:
http://myserver:8888/orabpel/default/MyService
6 comments:
Thnaks BOss :))
Thank you..It's too good. works :)
It worksss.... Thanks :)
Thank you.. It works. :)
Thank you.... :) it really works.:)
Thank you ,it workS!!!!
Post a Comment