Issue - 22 - Implicit <sequence> macro

[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 - 22 - Implicit <sequence> macro

Origin: Extracted from email Yuzo Fujishima, 11 Jun 2003
Date submitted: 11 June 2003
Submitter: Yuzo Fujishima, NEC Corporation
Description:
I would like to propose what may be called "implicit sequence".
Implicit sequence "macro": If multiple activities are placed in a 
process definition where only one activity is allowed per se, assume 
there is an implicit sequence activity that contains the activities. 
Example: 
Regard
  <scope>
   <receive/>
   <invoke/>
   <reply/>
  </scope>
as
  <scope>
   <sequence>     <!-- implicit sequence -->
    <receive/>
    <invoke/>
    <reply/>
   </sequence>
  </scope>

---

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 - 22 - [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.