Yes, I bind my service endpoint to com.sun.httpsoapbc-1.0-2 . I don't know if it's possible to combine components from different companies like Apache (Ode) and Sun (httpsoapbc).
I attach my service Assembly. http://www.nabble.com/file/6820/SynchronousSampleApplication.zip SynchronousSampleApplication.zip http://www.nabble.com/file/6821/OdeInNetBeans.png Alex Boisvert wrote: > > 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> >> >> > > -- View this message in context: http://www.nabble.com/ApacheODE-as-Service-Engine-in-OpenESB-tf3273448.html#a9187577 Sent from the Apache Ode User mailing list archive at Nabble.com.
