Issue - 133 - Access to unnamed fault bodies

[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 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 - 133 - Access to unnamed fault bodies

Status: open
Categories: Fault handling
Date added: 15 Jul 2004
Submitter: Yaron Y. Goland
Date submitted: 15 July 2004
Description: If a fault is caught using a catch all then how does one gain access to 
the name and value of the thrown fault?
If a fault is caught using a type catch with no name how does one gain 
access to the name? If only for logging purposes.
Submitter's proposal: We can define a variable on both catch all and type catch of type 
xs:any. In both cases the content of the variable would be a single 
element with the name of the fault. In the case of catch all the 
contents of that element would be the fault body. In the case of a 'type 
catch' it would be empty.
Changes: 15 Jul 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 - 133 - [anything]" or is a reply to such a message. If you want to formally propose a resolution, please start the subject line "Issue - 133 - 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).