Issue - 280 - Clarification needed on <throw>'s @variable

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 - 280 - Clarification needed on <throw>'s @variable
Status: received

Date added: 4 May 2006

Date submitted: 04 May 2006

Submitter: Mark Ford

Description: Section 10.6 describes the <throw> activity as having a name and an optional variable attribute. There are no restrictions placed on the type of variable that can used with a <throw>. The fault matching code outlined in Section 12.4 precludes the possibility of accessing non-element or non-message fault data that exists as part of a caught fault so it seems pointless to allow users to compose a <throw> that references a non-element or non-message variable.

Submitter's proposal: I propose the following change in Section 10.6 

From: 

The <throw> activity is used when a business process needs to signal an internal fault explicitly. A fault MUST be identified with a QName. The <throw> activity provides the name for the fault, and can optionally provide data with further information about the fault. A fault handler can use such data to handle the fault and to populate any fault messages that need to be sent to other services. 

To:  (2 sentences added to first paragraph indicated in bold) 

The <throw> activity is used when a business process needs to signal an internal fault explicitly. A fault MUST be identified with a QName. The <throw> activity provides the name for the fault, and can optionally provide data with further information about the fault. A fault handler can use such data to handle the fault and to populate any fault messages that need to be sent to other services. If the optional faultVariable attribute is specified then it MUST reference a variable of type element or message. This restriction on the variable type MUST be enforced during static analysis.

Changes: 4 May 2006 - new issue

To comment on this issue (including whether it should be accepted), please follow-up to this announcement on the 
 list (replying to this message should automatically send your message to that list), or ensure
the subject line as you send it starts "Issue - 280 - [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 - 280 - 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).