Re: [wsbpel] Issue 103 - draft proposal

[Alex Yiu <alex.yiu@oracle.com>]

Hi Danny,

Thanks for reviewing the proposal and asking questions. :-)

In your example, $foo//bar will yield a nodeset of two elements.

If that expression is used in <assign> of (executable) BPEL, that will 
trigger bpws:selectionFailure fault in runtime (as described in Section 
14.3).  A BPEL implementation can detect this problem with static 
analysis also.

People would use $foo/a/bar or $foo/b/bar instead for the assignment.

A similar situation would occur for current specification. E.g.:
<from variable="foo" part="a" query="/abc//def" />

I hope I have answered your question.
Thanks!


Regards,
Alex Yiu



Danny van der Rijn wrote:

>ok, here's a question for this new syntax.  in XPath one can use the
>"descendent" axis (shorthand //) to find all nodes that are children of a
>particular node.  assuming we have a WSDL variable 'foo' with 2 parts, a and
>b, and each part is an element whose name is 'bar':
>
>foo
>    - a - bar
>    - b - bar
>
>would an expression like exists($foo//bar) be one that we would allow?
>
>danny
>
>  
>