Re: [wsbpel] New issue proposal to handle the issue spawned from Issue120.02

[Danny van der Rijn <dannyv@tibco.com>]

Obviously, I disagree, but would be interested in hearing people's 
opinions one way or another.

Danny

Alex Yiu wrote:

>
>
> You mean part (b) and (c).
> If so, I would say those two parts bring in too much changes to the 
> spec without a sufficient set of benefits.
>
>
> Regards,
> Alex Yiu
>
>
> Danny van der Rijn wrote:
>
>> Please consider the other parts of 
>> http://lists.oasis-open.org/archives/wsbpel/200509/msg00083.html if 
>> you are looking at this one.
>>
>> Thanks
>> Danny
>>
>> ALEX.YIU@ORACLE.COM wrote:
>>
>>> 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
>>>
>>>  
>>>
>
>
>