Issue - 241 - clarification of onevent resource resolution

[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 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 - 241 - clarification of onevent resource resolution

Status: open
Date added: 10 Jan 2006
Categories: Scoping
Date submitted: 10 January 2006
Submitter: Alex.Yiu@oracle.com
Date accepted: 10 Jan 2006
Description: During the discussion of issue 120.2 : Correlation and zero part messages , Danny made a proposal to collapse onEvent and scope into one syntactic element. Some TC members expressed concern that it does not fit original 
Issue 120.2 description. Hence, I here propose a new issue and its description to follow that up.

There are a number of resources used by onEvent:

• partnerLink
• correlationSet
• messageExchange
• variables: message variable (based on "variable" attribute) and non message variable (based on <fromPart>)

(Note: now onEvent must have a scope associated with it. )

The resolution rule of those resources are a bit inconsistent and underspecified in the current text:

• partnerLink : resolved only to parent scope only
• correlation, messageExchange: resolved to both parent scope and associated scope
• variables and messageExchange: resolved to the associated scope only

We need to review these resolution policy, potentially make them more consistent and spell it out clearly in spec text.

In addition to resolution policy clarification and clearup, we may collapse the <onEvent> syntactic element with the <scope> syntactic element, if that make BPEL developers life easier (along the line of Danny's resolution. See link below)

See Danny van der Rijn, 13 Sep 2005
Changes: 10 Jan 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 - 241 - [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 - 241 - 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).