BPEL Descriptor Question

[ncapito]

So i have a process that is working however i have a question.


For any webservice that you call inside of a process you have to define where to get the wsdl... how is this done. I am currently doing this by defining the absolute location inside the bpel-definition.xml like this:

<imports>
 <wsdl namespace="http://webservice" location="http://localhost:8080/SimpleMessageWS/SimpleWriter?wsdl"/>
 <wsdl namespace="http://com.test.jtm.webservice/" location="JTMFusionCaller.wsdl"/>
 </imports>

Like i said this works but is this the correct way? It does not seem like a good standard because if the server address changes i am in trouble?





The same question applies for the bpel-application.xml

 <serviceCatalogs>
 <definitionCatalog>
 <definition location="http://localhost:8080/SimpleMessageWS/SimpleWriter?wsdl" />
 </definitionCatalog>
 </serviceCatalogs>

? Can someone please help?

[ncapito]

FYI it would be nice to have an example where the process calls an external webservice (not packaged within the process)....

[aguizar]

BPEL process definitions rely on WSDL abstract definitions (messages and port types) only. Just as in EJB development, the involved parties agree on a service interface; each party gets a copy of the interface documents and starts working separately on getting their side working.

Pointing to a deployed document from bpel-definition.xml is possible, but inconvenient for the very reason you mention. A better practice is downloading the document and removing the binding and service elements.

In the case of bpel-application.xml, you need a registry (such as a UDDI server) to shield you from changes in the partner endpoint addresses. That's in our roadmap but not available yet.

[ncapito]

I thank you for your help... i updated it with a local wsdl and it worked fine....