[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue - 277 - Clarification of fault handling at process level
This issue has been added to the wsbpel issue list with a status of "open". The TC agreed to accept the issue before it was added to the 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 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.
If the fault occurs in (or is rethrown to) the global process scope, and there is no matching faultHandler for the fault at the global level, the process terminates abnormally, as though an exit activity had been performed. See Implicit Fault and CompensationHandlers for a more complete description of the default fault and compensation handling behavior.
This removal is a normative change since the paragraph contained a description of the process ending as if an <exit> activity had executed. This language would prevent the execution of the default fault handler (and any resulting compensation) from the process scope.
Resolution: This issue was opened and approved during the San Jose face to face.
Changes: 3 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 - 277 - [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 - 277 - 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]