Hi Manu, Do you bind your service endpoint to a SOAP/HTTP binding component? If not, then you can't use sendsoap to invoke your process.
I would need your complete service assembly and your SOAP message to help. regards, alex On 2/27/07, Waxter <[EMAIL PROTECTED]> wrote:
I have updated OdeBpelEngine to the last release (512225) and now I can successfully deploy a Service Assembly in OpenESB with OdeBpelEngine as Bpel Service Engine instead com.sun.bpelse. As you noticed, Netbeans doesn't generate a deploy.xml descriptor, so I included it manually into SynchronousSample.jar Service Unit. OpenESB requires a jbi.xml descriptor too, so in the Service Unit exists both descriptors.... However when I send a soap message to the endpoint, I get a fault message like this: [EMAIL PROTECTED]:/opt/ode/examples$ sendsoap.sh http://localhost:18181/SynchronousSample test.soap <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/ "><SOAP-ENV:Header/><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Server</faultcode><faultstring>Unable to located activated endpoint for service connection {http://localhost/SynchronousSample/SynchronousSample}service1 port1.</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
