Issue - 78 - New value for initiate on multi-starts

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

This issue has been added to the wsbpel issue list. The issues list is posted as a Technical Committee document to the OASIS WSBPEL TC pages on a regular basis. The current edition, as a TC document, is the most recent document with the title in the "Issues" folder of the WSBPEL TC document list - the next posting will include this issue. The list editor's working copy, which will normally include an issue when it is announced, is available at this constant URL.

Issue - 78 - New value for initiate on multi-starts

Status: open
Date added: 22 Oct 2003
Submitter: Yaron Goland
Date submitted: 22 October 2003
Description: The use of the initiate attribute on correlations in
multi-start activities can easily lead to misunderstanding. The
'initiate='yes'' value is only true on the first multi-start activity
that fires, the rest are magically transformed into 'initiate='no''
once the first multi-start fires. One can easily imagine the resulting
confusion. To prevent this confusion perhaps we should add a new value
for initiate such as 'initiate='multistart''. This shows that the
programmer understands the special semantics of correlation sets on
multi-start activities.
Changes: 22 Oct 2003 - new issue

---

To comment on this issue, please follow-up to this announcement on the wsbpel@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 - 78 - [anything]" or is a reply to such a message.

To add a new issue, see the issues procedures document (but the address for new issue submission is the sender of this announcement).