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 - 274 - orphaned IMA in compensationHandler

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 - 274 - orphaned IMA in compensationHandler

Status: received
Date added: 2 May 2006
Date submitted: 02 May 2006
Submitter: Mark Ford
Description: Section 12 outlines four scenarios for handling the detection and reporting of errors for orphaned IMA's

1. Normal scope completion - scope activity and event handlers complete normally. The engine MUST check for orphaned IMA's within the completing scope and fault itself with a bpel:missingReply if found.

2. Fault handler completion without fault or rethrow. The engine MUST check for ophaned IMA's within the completing scope and fault its parent scope with a bpel:missingReply if orphaned IMA's found.

3. Fault handler completion with fault or rethrow. The engine MUST NOT check for orphaned IMA's. It is the responsibility of the parent scope to check for the orphaned IMA's and report them.

4. Termination handler completion. Same as scenario 3.

The above scenarios do not address a compensationHandler that completes with orphaned IMA's. In this scenario, a compensation handler opens an IMA as part of its execution using a partnerLink or messageExchange declared within its associated scope. At the time the compensationHandler completes it fails to reply to the open IMA which makes the IMA an orphan.
Submitter's proposal: My proposed resolution is to have the fault handler or termination handler that started the compensation routine responsible for handling the orphaned IMA's as outlined in the existing bullets. This could be made explicit as a new bullet or as a clarifying statement following the bullets. I propose adding a 5th bullet as follows.

Changes: 2 May 2006 - 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 - 274 - [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 - 274 - 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).

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