Issue - 23 - implicit links of the runtime engine

[ws-bpel issues list editor<peter.furniss@choreology.com>]

This issue has been added to the wsbpel issue list. It is in the current version of the list at wsbpel document 2656, It is hoped to have a fixed url for the ever-changing list.

Issue - 23 - implicit links of the runtime engine

Origin: Extracted from email Eckenfels. Bernd, 12 Jun 2003
Date submitted: 12 June 2003
Submitter: Bernd Eckenfels, Seeburger
Description:
while implementing the BPEL4WS specification, I noted a few simplifications, 
which can be added to the runtime mode:

- implicit flow-start links If the BPEL4WS parser adds links from a flow parent, to all the unlinked activities within, then the process engine does not have to search all activateable activities, but can just follow the links

- implicit sequence links Instead of a sequence, the engine can simply use a flow, where all sequenced activities are linked together, that way the engine has not to implement two different scope styles

I notice, that this is not so important for the spec, but especially the second case shows, that there is no need for the sequence activity from a control flow point of few. I guess it would be good to add some comments on this in the spec. Or do i have missed a sematical difference between a sequence and a flow with linked activities?

---

To comment on this issue, please follow-up to this announcement on the wsbpel-reqts@lists.oasis-open.org list (replying to this message should automatically send your message to that list), or ensure the subject line as you send it starts "Issue - 23 - [anything]".

To add a new issue, send email to the wsbpel requirements and issues coordination list, adding a proposed title for the issue to the subject line. See the issues procedures document for further information.