OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Issue - 204 - clarify the relationship between eventHandler and compensationHandler


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.

Issue - 204 - clarify the relationship between eventHandler and compensationHandler

Status: received
Date added: 20 Apr 2005
Categories: Compensation, Syntax and validation
Date submitted: 20 April 2005
Submitter: Alex Yiu
Description: Assuming a compensation-handler can be potentially used to compensate the work of event handlers, we should clarify:

either: restrict the child activity within an event handler always as a <scope> activity

or: state a precaution in the spec that a BPEL developer should use <scope> within event handlers whenever they want to do compensation work on event handlers
Submitter's proposal: IMHO, I prefer the former for usability and consistency, since we already disallow control-link crossing <eventHandler>
Changes: 20 Apr 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 - 204 - [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 - 204 - 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]