[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue - 216 - Compensation Handling and forEach
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.
<while>
like compensation semantics for
serial forEach.
The solution to parallel forEach depends on issue 204 : clarify the relationship between eventHandler and compensationHandler . If issue 204
is decided by requiring that eventHandlers contain <scope>
activities then the solution is to just specify that calling the scope
name inside of the forEach results in all the instances being
compensated in parallel (since links can't cross in or out of a forEach
or between scopes in a forEach there is no link ordering to worry about).
If issue 204 is decided by introducing ghost scopes then we will
probably have to treat each child scope as a separate 'while like'
entity that gets compensated as a unit.
Changes: 6 Jun 2005 - 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 - 216 - [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 - 216 - 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).
Choreology Anti virus scan completed
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]