Issue - 95 - Rethrow a Fault

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

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 - 95 - Rethrow a Fault

Status: open
Date added: 3 Feb 2004
Submitter: Dieter Koenig
Date submitted: 03 February 2004
Document: BPEL4WS 1.1 (May 5, 2003)
Description: A <catchAll> fault handler cannot rethrow the fault it has caught. Implicit fault
handlers always rethrow the fault. Therefore, one cannot express the default behavior in a
catchAll fault handler.

Specific fault handlers that catch a particular fault can rethrow the fault because they have the fault name and variable. However, a catchAll cannot because it does not know about the details of the fault.

A similar consideration applies to <catch> fault handlers that are able to accept different faults because they do not specify faultName AND faultVariable.
Submitter's proposal: Allow all fault handlers to rethrow the original fault. For example, this could be done by invoking <throw/> without attributes which would then mean that the original fault is rethrown.

Example:

   <catchAll>
      <sequence>
         ...
         <throw/> <!-- this is a rethrow of the original fault -->
      </sequence>
   <catchAll>

Changes: 3 Feb 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 - 95 - [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).