Issue - R15 - Fix description of abnormal process completion

[ws-bpel issues list editor<peter@furniss.co.uk>]

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 - R15 - Fix description of abnormal process completion

Status: received
Date added: 26 Sep 2006
Date submitted: 26 September 2006
Submitter: Mark Ford
Description: Section 5.5 contains a description of the lifecycle of a business process. This section contains some text which should have been modified as part of Issue 277. That issue removed some text which didn’t allow for a process level default fault handler to execute. The text in Section 5.5 makes a reference to that text. As it reads now, Section 5.5 implies that a process level default fault handler would not execute. The text should read that a process ends abnormally after its process level fault handler completes. There is also a new case where a process level fault handler could itself fault which would cause the process to end immediately.

Thanks to Monica for finding this inconsistency and Alex for providing some edits.
Submitter's proposal:

Change paragraph in Section 5.5 FROM:

A business process instance ends either normally or abnormally. The process ends normally when the main activity of the process completes. The process ends abnormally if either:

• a fault reaches the process scope, regardless of whether it is handled or not (see section 10.10. Immediately Ending a Process – Exit), or
• the process instance is explicitly ended by an exit activity (see section 10.10. Immediately Ending a Process).

TO:

A business process instance ends either normally or abnormally. The process ends normally when the main activity of the process completes. The process ends abnormally if either:

• a process level (explicit or default) fault handler completes or
• the execution of a process level fault handler itself faults (the effect of this particular case is similar to an <exit> activity or
• the process instance is explicitly ended by an exit activity (see section 10.10. Immediately Ending a Process).

Changes: 26 Sep 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 - R15 - [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 - R15 - Proposed resolution", without any Re: or similar.

To add a new issue, see the issues procedures document