Diff for How to resolve a BPEL Xpath query in WSDL?
22. November 2009 - 20:02 by jonlee | 22. November 2009 - 20:04 by jonlee | ||
---|---|---|---|
< previous diff | next diff > | ||
Changes to Body | |||
Line 18 | Line 18 | ||
</p>
| </p>
| ||
<p>
| <p>
| ||
- | The question is how can I take the BPEL query "<strong>/e:AuctionResult[2]/@AuctionID</strong>" as an input and perfrom a right Xpath query in WSDL? Because when BPEL query uses some additional XPath library, the problems are complex to translate to the right XPath query as above.
| + | The question is how can I take the BPEL query "<strong>/e:AuctionResult[2]/@AuctionID</strong>" as an input and perfrom a right Xpath query in WSDL? Because when BPEL query uses some additional XPath functions library, the problems are complex to translate to the right XPath query as above.
|
</p>
| </p>
| ||
<p>
| <p>
|
How to resolve a BPEL Xpath query?
Hi,
I have a question about XPath query in WSBPEL. Its Xpath query is not the same as a normal Xpath.
Let's take an example from WSBPEL 2.0 specification, a BPEL query:
<from>$Results/e:AuctionResult[2]/@AuctionID</from>
but a normal XPath1.0 should perform something like:
e:complexType[@name='AuctionResults']/e:sequence/e:element[name='AuctionResult']... --> BPEL query cares only about the ELEMENT NAME and ATT name.
The question is how can I take the BPEL query "/e:AuctionResult[2]/@AuctionID" as an input and perfrom a right Xpath query in WSDL? Because when BPEL query uses some additional XPath functions library, the problems are complex to translate to the right XPath query as above.
Hope someone would help
I'm really appreciate. Thank you very much
------------------------------------------------------------------------------------------------------------
<xsd:complexType name="AuctionResults">
<xsd:sequence>
<xsd:element name="AuctionResult" maxOccurs="unbounded"
form="qualified">
<xsd:complexType>
<xsd:attribute name="AuctionID" type="xsd:int"/>
<xsd:attribute name="Result" type="xsd:string"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>