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 - 108 - Parallel Compensation

This issue has been added to the wsbpel issue list. 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 document with the title in the "Issues" folder of the WSBPEL TC document list - the next posting 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 - 108 - Parallel Compensation

Status: open
Area: Compensation
Date added: 20 Mar 2004
Submitter: Yaron Y. Goland
Date submitted: 19 March 2004
Description: If someone is willing to do manual compensation then they could, at least in theory, do parallel compensation today by including calls to compensate with the names of the child scopes inside of a flow. E.g.
       compensate scope="foo"
       compensate scope="bar"
In the case of the default compensation handler section 13.3.3 of the latest editor's draft states "If the compensation handler for a scope is absent, the default compensation handler invokes the compensation handlers for the immediately enclosed scopes in the reverse order of the completion of those scopes."

But, if one felt deeply sneaky, one could interpret the spec to mean that one must start the compensation handlers in the completion order but there is no requirement that one must necessarily wait for a compensation handler to complete execution before starting the next one. In other words, one could interpret the current language as allowing default compensation handlers to execute child compensation handlers in parallel.

The purpose of this issue is to clarify the ability to run compensation handlers in parallel so that programmers know what to expect. Since we now allow compensation handlers to manipulate common variables it is critical that programmers know if their handlers can run in parallel.

At a minimum this issue should answer the following questions:

Changes: 20 Mar 2004 - new issue

To comment on this issue, 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 - 108 - [anything]" or is a reply to such a message.

To add a new issue, see the issues procedures document (but the address for new issue submission is the sender of this announcement).

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