[Users] Problems for executing nested receives in BPEL

[jlesbegueries [via Petals ESB]]

Hi,

In the logic of the workflow, I would add an invoke after the first receive
in order to notify the 2nd partner it can invokes the BPEL. (This new invoke
can be a InOnly message). Then, in order no to get the BPEL process lost,
you should use "correlations". This concept is defined in BPEL in order to
correlate messages according to one process instance.

For instance, the InOnly invoke can send an id built from the 1st receive
input data. Then the 2nd partner can send its request with this id set in
its request.

A classic usecase about correlations is the travel agency usecase, explained
in this page

http://doc.petalslink.com/display/easybpel/Chapter+1.+Use-cases



_______________________________________________
If you reply to this email, your message will be added to the discussion below:
http://forum.petalslink.com/Problems-for-executing-nested-receives-in-BPEL-tp3258887p3297847.html
To start a new topic under Users (get help, provide help), email ml-node+2681628-1333396262-385891 at n3.nabble.com
To unsubscribe from Users (get help, provide help), visit http://forum.petalslink.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2681628&code=dXNlcnNAZm9ydW0ucGV0YWxzbGluay5vcmd8MjY4MTYyOHwtOTE3MDU0NjU4
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://forum-list.petalslink.org/pipermail/users/attachments/20110831/5b92e9ef/attachment.htm>