Looks like ODE is using WS-BPEL 2.0 semantics here, although I'm a little surprised that /ns8:auth worked. I would have expected the context for the query to be the document element for the message part.
On Tue, May 24, 2011 at 9:58 PM, Tim Buss <[email protected]> wrote: > A further clarification. > > As best I can tell, and the documentation on this is rather sparse, the > locationPath query for BPEL4WS 1.1 should either be rooted on the part name > if the part is defined using a type (typical for RPC literal style wsdls) or > of the part name is defined using an element (typical for document literal > wsdls) then the element name should be used. In the example I gave, the > service is document literal and the element name that defines the part in the > wsdl is ns8:GetProjects. Hence it seems the required Xpath query should be > "/ns8:GetProjects/ns8:auth". If the service had been rpc literal then the > required xpath should be "parameters/ns8:auth" since the part is named > "parameters". > > On debugging it seems that Ode 1.3.5 creates a variable the represents the > part that appears to be in a document message/parameters/ns8:GetProjects. > However, Ode the requires the xpath query to be either "ns8:auth" or > "/ns8:auth" to successfully select the ns8:auth element, both of which seem > odd. > > Regards, > Tim >
