Issue - 256 - ExtensionActivity and Start Activities

[ws-bpel issues list editor <peter.furniss@erebor.co.uk>]

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 - 256 - ExtensionActivity and Start Activities

Status: received
Date added: 29 Mar 2006
Categories: activities
Date submitted: 29 March 2006
Submitter: Dieter Koenig1
Document: WS-BPEL 2.0 Specfication (March 29, 2006)
Description: The relationship between the <extensionActivity> (defined in
10.9) and start activities (defined in 10.4) must be clarified.

Section 10.9 today has the following text:

> If the element contained within the extensionActivity element is not recognized by the WS-BPEL processor and is not subject to a mustUnderstand="yes" requirement from an extension declaration then the unknown activity MUST be treated as if it were an empty activity.

Section 10.4 today has the following text:

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

This leaves situations unspecified where an <extensionActivity> is itself a start activity or (as a structured activity) contains a start activity.
Submitter's proposal: Add the following to the explanation of <extensionActivity> (in 10.9):

> If an <extensionActivity> child element is itself a start activity or contains a start activity then the namespace of the <extensionActivity> child element MUST be declared with mustUnderstand="yes".

In addition, rephrase the statement about start activities and include the <extensionActivity> (in 10.4):

The only activities that are allowed to be performed prior to or simultaneously with a "start activity" are scope, flow, sequence, empty, or an extensionActivity with the following characteristics:

• the namespace of the <extensionActivity> child element MUST be declared with mustUnderstand="yes"
• the <extensionActivity> child element MUST be a structured activity containing the "start activity"
• the <extensionActivity> child element MUST NOT be a repeatable activity

Changes: 29 Mar 2006 - new issue

---

To comment on this issue (including whether it should be accepted), 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 - 256 - [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 - 256 - 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).