Just to let you know that for BPEL we are only supporting ActiveEndpoints at this stage.
Have you tried the contract.war?
look for the service, click on the link and get the WSDL?
In any case, the WSDL through/mediated the ESB is virtually the same as the WSDL directly to the JBossWS endpoint aside from the port number.
Exploring the 'contract' web application I found the URL to register Partner Service under JBPM-BPEL but it is not the JBossWS endpoint with a different port number.
I've registered the service using
Is this an undocumented/not supported feature? Subject to change?
What do you mean "undocumented"? Support for only ActiveEndpoints BPEL is well documented in the ESB.
We have never tested the mediation of a jBPM-BPEL Endpoint via the ESB. Only regular JBossWS endpoints and integration with Active Endpoints BPEL have been tested.
Can you list the steps taken to verify that the WS endpoint (jBPM-BPEL I assume) is available?
You should see it originally under http://localhost/jbossws
If you can find it there then you can setup the jboss-esb.xml like you would in webservice_producer.
Do spend some time figuring out how the webservice_bpel works with AE (and the other WS examples work), then you might be able to extract the knowledge you need to be successful here.
First of all: Our test application is running!
To ensure that we have defined a legal scenario (without ActiveEndpoints) I would like to clarify our approach.
We have installed two server instances:
- one JBoss AS 4.2.1 GA with a JBPM-BPEL 1.1.GA. (server instance A)
- one JBoss ESB 4.2.1 GA (server instance B)
Then we have deployed a WS on B and provided a jboss-esb.xml configuration via *.esb deployment (based on webservice-producer example).
After that we have defined and registered a BPEL process on A that uses the 'plain' WS on B. (The WS was registered as Partner Service in jbpm-bpel console on A using 'http://myhost:8080/testWS/TestWS?wsdl').
The BPEL process is running and calls the WS directly.
In the next step we tried to connect to the ESB mediated WS. (The WS was registered as Partner Service in jbpm-bpel console on A using 'http://myhost:8080/contract/contract.jsp?serviceCat=MyServiceCategory&serviceName=MyWSTESTService&protocol=http')
The BPEL process is running and calls the actions defined in jboss-esb.xml (print-before, JBossWSAdapter that calls TestWS and print-after).
Is the definition of the Partner Service in JBPM-BPEL using following base location 'http://myhost:8080/contract/contract.jsp?serviceCat=MyServiceCategory&serviceName=MyWSTESTService&protocol=http'
the recommended approach?