[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue - 39 - Inconsistent syntax for query attribute values in spec examples
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 document with the title wsbpel_issues_list.html in the "Issues" folder of the WSBPEL TC document list - the next posting 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.
On page 38:
<bpws:propertyAlias propertyName="tns:taxpayerNumber" messageType="txmsg:taxpayerInfo" part="identification" query="/socialsecnumber"/>instead of query="/identification/socialsecnumber"
On page 49:
<bpws:propertyAlias propertyName="cor:customerID" messageType="tns:POMessage" part="PO" query="/PO/CID"/>(and similarly the three following propertyAlias elements in the same example)
On page 92:
<bpws:propertyAlias propertyName="tns:shipOrderID" messageType="sns:shippingNoticeMsg" part="shipNotice" query="/ShipNoticeHeader/shipOrderID"/>instead of query="/shipNotice/ShipNoticeHeader/shipOrderID" (and similarly the four following propertyAlias elements in the same example)
It seems that the example on page 49 is correct and the other ones are wrong.
In fact, sec. 14.3, Assignment, says:
"For XPath 1.0, the value of the query attribute MUST be an absolute locationPath (with '/' meaning the root of the document fragment representing the entire part). It is used to identify the root of a subtree within the document fragment representing the part."and sec. 8.2, Defining Properties, says:
"The interpretation of the message, part, and query attributes is the same as in the corresponding from-spec in copy assignments (see Assignment).
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 - 39 - [anything]".
To add a new issue, see the issues procedures document.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]