Issue - 273 - Removing capability of <empty> to execute prior to createInstance

This issue has been added to the wsbpel issue list with a status of "received".
The status will be changed to "open" if a motion to open the issue is proposed and that
motion is approved by the TC. A motion could also be proposed to close it without
further consideration. Otherwise it will remain as "received".

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 version of 
the document entitled  in the 
"Issues" folder of the WSBPEL TC document list
- the next posting as a TC document 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 - 273 - Removing capability of <empty> to execute prior to createInstance
Status: received

Date added: 2 May 2006

Date submitted: 02 May 2006

Submitter: Mark Ford

Description: An <empty> activity is listed as one of the acceptable "non-start" activities that may be performed prior to or simulataneously with a "start activity". This text was introduced with the resolution for Issue 81. 

This was discussed during the April 24-28 meeting and the general consensus was to remove <empty> from the list. Since this is a normative change, a new issue is being opened for any further discussion.

As discussed during the meeting, allowing an <empty> to execute prior to a start activity seemed out of place since all of the other activities were container activities in which the start activity would have been embedded. Furthermore, allowing an <empty> to execute prior to the start activity introduces the possibility that outbound links from the <empty> might fire and trigger the execution of other types of activities prior to the execution of the start activity. Based on these issues, the proposal is to remove the <empty> from this list.

Submitter's proposal: The proposed change is in Section 10.4 

From: 

NO other "non-start activities" but scope, flow, sequence or empty activities may potentially be performed prior to or simultaneously with a "start activity". 

To: 

NO other "non-start activities" but scope, flow, or sequence activities may potentially be performed prior to or simultaneously with a "start activity". 

Changes: 2 May 2006 - new issue

To comment on this issue (including whether it should be accepted), please follow-up to this announcement on the 
 list (replying to this message should automatically send your message to that list), or ensure
the subject line as you send it starts "Issue - 273 - [anything]" or is a reply
to such a message. If you want to formally propose a resolution to an open issue, please start the subject line 
"Issue - 273 - Proposed resolution", without any Re: or similar.

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