7 messages in org.oasis-open.lists.wsbpelNew issue proposal to handle the issu...| From | Sent On | Attachments |
|---|---|---|
| ALEX...@ORACLE.COM | Jan 10, 2006 8:12 am | |
| ws-bpel issues list editor | Jan 10, 2006 2:07 pm | |
| Peter Furniss | Jan 10, 2006 3:21 pm | |
| Danny van der Rijn | Jan 10, 2006 6:15 pm | |
| Danny van der Rijn | Jan 10, 2006 6:16 pm | |
| Alex Yiu | Jan 10, 2006 6:20 pm | |
| Danny van der Rijn | Jan 10, 2006 6:23 pm |
| Subject: | New issue proposal to handle the issue spawned from Issue 120.02 | |
|---|---|---|
| From: | ALEX...@ORACLE.COM (ALEX...@ORACLE.COM) | |
| Date: | Jan 10, 2006 8:12:17 am | |
| List: | org.oasis-open.lists.wsbpel | |
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