Issue - 25 - Consistent enablement of compensation handlers

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

This issue has been added to the wsbpel issue list. It is in the current version of the list at wsbpel document 2656, It is hoped to have a fixed url for the ever-changing list.

Issue - 25 - Consistent enablement of compensation handlers

Submitter: Assaf Arkin
Date submitted: 25 June 2003
Categories: clarification/enhancement
Document: Specification
Description:

What are the semantics of a compensation handler specified for the business process as a whole when the enableInstanceCompensation attribute is set to "no"? If instance compensation is not enabled then it should be an error to define a compensation handler. This should be clarified. If the intent is to disable default compensation when no compensation handler is defined then another alternative is to assume that no compensation is possible if no compensation handler is defined (and the same for scopes). A default compensation handler would take the form of:

<compensationHandler> <compensate/> </compensationHandler>

Although this require more XML elements to be defined, it allows the compensation handling behavior to be turned on and off for the process and a scope by simply electing not to define a compensation handler. At any rate, the ability to disable compensation for a scope is also required if a process attempts to invoke compensation handlers for invoked services from compensation handlers associated with the invoke activity's scope.

---

To comment on this issue, please follow-up to this announcement on the wsbpel-reqts@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 - 25 - [anything]".

To add a new issue, send email to the wsbpel requirements and issues coordination list, adding a proposed title for the issue to the subject line. See the issues procedures document for further information.