Invoking a web service deployed in a different host is no different than invoking one
deployed in the local host. It is just a matter of referencing the remote WSDL document
from your service catalog instead of referencing a local document.
That said, here is what I would do:
Save the external WSDL document locally.
At design time, the BPEL process is only concerned with the messages and port types of
partner services. So I remove the binding and service elements from my *local* WSDL, and
reference it from bpel-definition.xml
I package the BPEL process and my local WSDL document in the jBPM process archive.
Once I'm ready to deploy, the process will need the binding and service information to
actually invoke the service. So I reference the external WSDL document from
bpel-application.xml.What is the point of this two-step approach? Well, it allows for
building your process by contract. You can define your process in its entirety even before
the partner services are deployed. You can test your process using local versions of the
partner services. Once they become available, all you need to do is update your service
catalog and you are done.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4020374#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...