I'm not too familiar with Sun's httpbc but I think should you match the
service endpoint in deploy.xml to the connections in the service assembly's
jbi.xml and the services in the BPEL service unit's jbi.xml, like this:
http://ode.fivesight.com/schemas/2006/06/27/dd";
xmlns:pns="
http://en
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
SynchronousSampleApplic
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 O
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
Synchronou
Another important thing I should mention... Ode currently requires a custom
deployment descriptor (deploy.xml) to bind process endpoints. NetBeans
does not generate this file so I believe you'll have to create it yourself
and add it to your service units.
There an example here:
http://svn.apa
Hi Manu,
The root error is most likely in the server-side log file. Can you set
your logging configuration at DEBUG for "org.apache.ode" and see if you get
better diagnosis information?
Also, I've just committed a fix for the surface error you encountered. Ode
was returning a status code "FAI
