Issue - 163 - languageExecutionFault

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

This issue has been added to the wsbpel issue list with a status of "received". The status will be changed to "open" if the TC accepts it as identifying a bug in the spec or decides it should be accepted specially. Otherwise it will be closed without further consideration (but will be marked as "Revisitable")

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 - 163 - languageExecutionFault

Status: received
Date added: 22 Sep 2004
Categories: Syntax & validation
Date submitted: 22 September 2004
Submitter: Danny van der Rijn
Description: If a language that is executing subordinate to BPEL (e.g. 
XPATH) throws a fault, there is no current spec language that defines 
what to do with it.  This proposal clarifies that behavior.
Submitter's solution: To add a new standard fault, languageExecutionFault, which is 
thrown if the expression language or xxx throws an unhandled fault.

Add to the end of section 14.1 "If execution of the expression language yields an unhandled fault, the standard fault languageExecutionFault is thrown."

Add to the end of section 14.3 "If execution of the query language yields an unhandled fault, the standard fault languageExecutionFault is thrown."

Question: Should this fault define a message type (or should a generic message type be defined) to carry any additional data that is received from the executing language?
Changes: 22 Sep 2004 - 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 - 163 - [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 - 163 - 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).