New issue proposal clarification of onevent resource resolution

[Diane Jordan <drj@us.ibm.com>]

With the corrected name of the issue
as in the subject line, the TC decided to open this as a new issue. Please
assign a number for it. 

Regards, Diane
IBM  Emerging Internet Software Standards
drj@us.ibm.com
(919)254-7221 or 8-444-7221, Mobile: 919-624-5123, Fax 845-491-5709

----- Forwarded by Diane
Jordan/Raleigh/IBM on 01/10/2006 11:37 AM -----

ALEX.YIU@ORACLE.COM

01/10/2006 11:12 AM

To	wsbpel@lists.oasis-open.org
cc	alex.yiu@ORACLE.COM
Subject	[wsbpel] New issue proposal to handle the issue spawned from Issue 120.02

During the discussion of Issue 120.2, 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)

http://lists.oasis-open.org/archives/wsbpel/200509/msg00024.html


Thanks


Regards,
Alex Yiu



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs
in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php