Issue - 233 - Invoking Compensation Handler From Termination Handler

[ws-bpel issues list editor <peter.furniss@choreology.com>]

This issue has been added to the wsbpel issue list with a status of "received". The status will be changed to "open" if a motion to open the issue is proposed and that motion is approved by the TC. A motion could also be proposed to close it without further consideration. Otherwise it will remain as "received".

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 - 233 - Invoking Compensation Handler From Termination Handler

Status: received
Date added: 10 Nov 2005
Categories: Compensation, Termination
Date submitted: 10 November 2005
Submitter: Yuzo Fujishima
Document: 01SEP2005 Draft
Description: In 13.3.3. Invoking a Compensation Handler, it is stated that compensate activity can be invoked only from within a fault handler or a compensation handler.

13.3.3, paragraph 3

The ability to explicitly invoke the compensate activity is the underpinning of the application-controlled error-handling framework of WS-BPEL. This activity can be used only in the following parts of a business process:

• In a fault handler of the scope that immediately encloses the scope for which compensation is to be performed.

• In the compensation handler of the scope that immediately encloses the scope for which compensation is to be performed.

But to be consistent with the fact that the default termination 
handler performs compensation as stated in 13.4.4. Semantics of 
Activity Termination, compensate activity should be able to be invoked from within a termination handler also.

13.4.4, end of paragraph 4:

>   Following this, the custom termination handler for the scope, 
>   if present, is run. If the custom termination handler is missing,
>   the default termination handler performs compensation of all
>   successfully completed nested scopes in the same order as in the
>   case of a default fault handler.

Submitter's proposal:

Change the specification such that invoking compensate activity from within a termination handler is allowed. More concretely, add the following to 13.3.3 quoted above:

• In the termination handler of the scope that immediately encloses the scope for which compensation is to be performed.

Champions: Yuzo Fujishima <fujishima@bc.jp.nec.com> 
Changes: 10 Nov 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 - 233 - [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 - 233 - 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).