Please see replies below.
LeeHoHun wrote:
Hi all
I'm trying to work with the latest version servicemix + ode-jbi. and I
tested HelloWorld2 Process and work fine.
I've changed the HelloWorld2 process to invoke the External WS that I made.
but while deploying it, a following error has occured.
ERROR - BpelServer
org.apache.ode.bpel.engine.BpelServerImpl.
start(BpelServerImpl.java:151) - Error activating process
{urn:/HelloWorld2.bpel}HelloWorld2
org.apache.ode.bpel.iapi.ContextException: Unkown endpoint:
{http://www.daesangit.com/LoginMgr.jws}LoginMgr:LoginMgrSoap
so I have three question .
1. could you explain to me why this error comes,
The JBI IL cannot resolve the ServiceEndpoint with qname
"{http://www.daesangit.com/LoginMgr.jws}LoginMgr"; and port
"LoginMgrSoap". Are you sure your component is deployed and this
ServiceEndpoint is activated? It might be worthwhile to post your full
deployment unit.
2. should I config another thing to invoke External WS?
To invoke an external web service, you must generally setup a binding
component (e.g. servicemix-http) to act a gateway to the external service.
3. when ode-jbi BPEL process calls External WS, it must go through the JBI?
Yes, ode is just a service engine and does not provide any binding
component of its own. Like other JBI service engines, it's designed to
leverage your JBI environment.
4. I think whole BPEL process action(invoke, receive, callback etc.) shoud
be done in just one process in ODE-JBI Engine without using JBI ServiceUnit.
I don't understand what you mean here; can you elaborate?
alex
