OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel-reqts message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: New Issue - Incomplete XPath expressions in the specification

Isn't this covered in issue 46 (see
and referenced in issue 39 (both now resolved).

Also, I see, if what the membership and attendance information Kavi
shows me is correct, you are still only a Prospective Member and it's
possible you ought to have been dropped back to Observer.  After I put
in your previous issue (now issue 90) there was some question as to
whether prospective members could post issues.  In practice, that might
differ as to whether the issue is a straightforward correction (as this
would be, if it weren't for 46) or a judgement or style question (as
this might be).  When do you hope to become a full member ?

(copying the issues and requirements group for advice)

Peter Furniss
Chief Scientist, Choreology Ltd
web: http://www.choreology.com
email: peter.furniss@choreology.com
phone: +44 870 739 0066
mobile: +44 7951 536168

> -----Original Message-----
> From: Kristofer Agren [mailto:kagren@pakalert.com]
> Sent: 16 February 2004 16:11
> To: Furniss, Peter
> Subject: New Issue - Incomplete XPath expressions in the specification
> Document: BPEL Specification
> Description:
> Many of the BPEL examples that are included in the
> specification use XPath queries that do not contain namespace 
> references. If the node(s) being selected are within a 
> namespace, per the XPath 1.0 specification, the XPath query 
> should reference the nodes by their expanded-name/fully 
> qualified name. 
> For example, in the excerpt below, the "query" attribute
> defines an XPath query without namespace references, although 
> that from the WSDL definition it is clear that the 
> complexType (ship:shipOrder) that defines the part is 
> contained in a namespace.
> <bpws:propertyAlias propertyName="tns:shipOrderID"
> 	messageType="sns:shippingRequestMsg"
> 	part="shipOrder"
> 	query="/shipOrder/ShipOrderRequestHeader/shipOrderID"/>
> The correct XPath query should be (assuming that the "ship"
> prefix is defined and accurate):
> query="/shipOrder/ship:ShipOrderRequestHeader/ship:shipOrderID"
> I propose that all XPath queries in the BPEL specification
> are updated to include namespace prefixes wherever applicable.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]