+1
We've been using XPath variables in that capacity (1.0 and 2.0) and it
works pretty well. The mapping from a WSDL-defined message to an infoset
is fairly straight forward and you get the benefit of static analysis
and no special restrictions on the usage of XPath 1.0/2.0 or XQuery.
Assaf
Yaron Y. Goland wrote:
> The more I think about 103 the better an idea I think it is.
>
> I wonder if we couldn't possibly make it work for WSDL types messages?
> Could we say that if the variable is of type WSDL message then there
> MUST be at least one path segment attached to it and that the path
> segment MUST be the name of a part in the WSDL message?
>
> Yaron
>
> To unsubscribe from this mailing list (and be removed from the roster
> of the OASIS TC), go to
> http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.php.
>
