Hi Michael,
Thank you many times, you save me from the wrong way. Since you are a master, would you please give me a light on this following rule under 8.2.4:
"When XPath 1.0 is used as an _expression_ language in WS-BPEL there is no context node available. Therefore the legal values of the XPath Expr (http://www.w3.org/TR/xpath#NT-Expr) production must be restricted in order to prevent access to the context node.
--> but why we can use:
<from>$variable.part/a/b/c</from>???
What is the restriction of XPath under 8.2.4? Although I google all the time. But I haven't really understand it yet.
Thank you again.
and have a nice day
--- On Tue, 11/24/09, Michael Illiger2 <MILLIGER@xxxxxxxxxx> wrote:
From: Michael Illiger2 <MILLIGER@xxxxxxxxxx> Subject: Re: [bpel-dev] The design tool different from OASIS specification for BPEL2.0 To: "BPEL Designer project developer discussions." <bpel-dev@xxxxxxxxxxx> Date: Tuesday, November 24, 2009, 8:29 PM
Hey Joni, You are not on the latest version of the BPEL 2.0 spec. (http://docs.oasis-open.org/wsbpel/2.0/wsbpel-v2.0.html) Here it says in chapter 8.4: The from-spec MUST be one the following variants: <from variable="BPELVariableName" part="NCName"?>
<query queryLanguage="anyURI"?>?
queryContent
</query>
</from>
<from partnerLink="NCName" endpointReference="myRole|partnerRole" />
<from variable="BPELVariableName" property="QName" />
<from expressionLanguage="anyURI"?>_expression_</from>
<from><literal>literal value</literal></from>
<from/>
|