[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue - 181 - uninitializedVariable cleanup
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.
Appendix 1 in table A.1 in the row marked uninitializedVariable currently states "Thrown when there is an attempt to access the value of an uninitialized part in a message variable."
In both cases there is a presumption that variables can only be of WSDL message type.
Thanks to Ron Ten-Hove for finding this problem.
Submitter's proposal: Change the text in 14.2 to read: "An attempt during process execution to use a variable or in the case of a message type variable a part of a variable before it is initialized MUST result in the standard bpws:uninitializedVariable fault."
Change the text in table A.1 to read: "Thrown when there is an attempt
to access the value of an uninitialized variable or in the case of a
message type variable one of its uninitialized parts."
Changes: 10 Dec 2004 - new issue
To comment on this issue (including whether it should be accepted), please follow-up to this announcement on the firstname.lastname@example.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 - 181 - [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 - 181 - 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).
Choreology Anti virus scan completed