Issue - 162 - Unique Activity Names for Compensate

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

This issue has been added to the wsbpel issue list with a status of "received". The status will be changed to "open" if the TC accepts it as identifying a bug in the spec or decides it should be accepted specially. Otherwise it will be closed without further consideration (but will be marked as "Revisitable")

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 - 162 - Unique Activity Names for Compensate

Status: received
Date added: 8 Sep 2004
Categories: Syntax and validation
Date submitted: 07 September 2004
Submitter: Dieter Koenig
Document: Specification working draft 1.39, Chapter 13.3.3, "Invoking a Compensation Handler".
Description: Currently, there is no constraint on activity names, i.e. the activity name (standard
attribute) does not have to be unique. As a result, a compensate activity may become ambigous:

scope
    compensationHandler
        compensate "A" <-- don't know which one
    scope name="A" <-- first enclosed scope
    scope name="A" <-- second enclosed scope

Submitter's proposal: Clarify that activity names used in a compensate activity must be unique within the scope.
Changes: 8 Sep 2004 - 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 - 162 - [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 - 162 - 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).