-
1. Re: jBPM BPEL Beta2: invoke an external web service
aguizar Dec 22, 2006 1:19 PM (in response to sergstone)Hi Serg,
You are right ? somehow, when I updated the user guide for version 1.1.Beta2, I left out the explanation of the bpel-application.xml descriptor. You can find the missing explanation in section 4.3.6.2 of the user guide for 1.1.Beta1. In addition, the XML Schema document for this descriptor resides in src/bpel/org/jbpm/bpel/xml/util/bpel_application_1_0.xsd.
I created BPEL-219 to track this issue.
Happy holidays! -
2. Re: jBPM BPEL Beta2: invoke an external web service
sergstone Dec 25, 2006 5:17 AM (in response to sergstone)Hi, Alex!
But there were some changes in the BPEL application descriptor (bpel-application.xml) as I can see. 1.1.Beta1 documentation introduces use of JMS in constructions like this:
<message-destination-ref-name>jms/atmRelation</message-destination-ref-name>
<message-destination-type>javax.jms.Queue</message-destination-type>
<message-destination-usage>ConsumesProduces</message-destination-usage>
along with a Relation servlet. org.jbpm.bpel.relation.jms.RelationServlet
1.1.Beta2 ATM example uses Integration servlet and no <resource-ref> or <message-destination-ref> elements.
Which one is correct? I specified for my external service, added to the bpel-application.xml but still couldn't get the example working. The error message has changed to
Caused by: java.lang.RuntimeException: service not found: service={ru:softech:HelloBook:warehouse}Warehouse
What's wrong?
Thank you in advance,
Serg
BTW, I'm wondering if BPEL extension supports clustering and if so what kind of clustering it supports and how?
Once again thanks a lot and Merry Christmas! -
3. Re: jBPM BPEL Beta2: invoke an external web service
aguizar Dec 27, 2006 4:57 AM (in response to sergstone)Please post your bpel-application.xml along with the WSDL document of your partner services.