ws-bpel issues list editor (pete...@choreology.com)
Jun 23, 2005 1:19:54 am
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
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 - 219 - correlationViolation from bad propertyAlias ?
Date added: 23 Jun 2005
Categories: Fault handling
Date submitted: 22 June 2005
Submitter: Alex Yiu
Description: when propertyAlias fails to execute property due to
query-language related problem], which fault will be thrown?
If my memory about the spec is correct, the spec is not clear on: when
propertyAlias fails to execute property [due to query-language related
problem], which fault will be thrown? correlationViolation fault?
For example, whether we will encounter selectionFailure or
correlationViolation fault, if the propertyAlias used in correlationSet does
not return one single value. [E.g. "./poHeader/@poID" (used in propertyAlias)
returns zero node]
Changes: 23 Jun 2005 - new issue
To comment on this issue (including whether it should be accepted), please
follow-up to this announcement on the wsb...@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 - 219 -
[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 - 219 -
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).