[jira] Updated: (ODE-369) Express Yourself - With XQuery

["Karthick Sankarachary (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ODE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karthick Sankarachary updated ODE-369:
--------------------------------------

    Attachment: xquery-support-for-branch.txt

We now support XQuery as a first-class expression language in WS-BPEL. 

To make this happen, it became clear early on that we had to upgrade to the latest and greatest version of Saxon. In the process, we discovered an issue with its JAXP functionality, which is now captured at the following link:

https://sourceforge.net/tracker/index.php?func=detail&aid=2149517&group_id=29872&atid=397617

Needless to say, this ODE patch would not have been possible without the above Saxon patch. Thanks to Michael Kay for taking the time to address our test case and giving us the patch!

Cheers,
Karthick Sankarachary



> Express Yourself - With XQuery
> ------------------------------
>
>                 Key: ODE-369
>                 URL: https://issues.apache.org/jira/browse/ODE-369
>             Project: ODE
>          Issue Type: New Feature
>          Components: BPEL Runtime
>    Affects Versions: 1.2
>         Environment: platform-independent
>            Reporter: Karthick Sankarachary
>             Fix For: 1.3
>
>         Attachments: xquery-support-for-branch.txt
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> By default, the language employed in WS-BPEL queries and expressions is XPath 1.0. This is denoted by the default value of the queryLanguage and expressionLanguage attributes, which is "urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0". In addition, we have out-of-the-box support for XPath 2.0.
> Given that XQuery 1.0 is fast becoming the de-facto lingua franca for querying XML, it is only fitting that it be given first-class status in WS-BPEL. Specifically, XQuery 1.0 goes above and beyond XPath 2.0 by offering the capability to write conditional/switch/iterating expressions, construct static/computed nodes, declare functions/variables, among other things.
> To that end, we propose leveraging WS-BPEL's extension mechanism to support the use of XQuery 1.0 as a query and expression language. In particular, XQuery 1.0 will be indicated by a specific value of the queryLanguage and expressionLanguage attribute, namely urn:oasis:names:tc:wsbpel:2.0:sublang:xquery1.0".
> The context for XQuery must be initialized with a set of bindings for in-scope variables, declarations of in-scope namespaces and a library of WS-BPEL and core XPath functions. In theory, one may import external XQuery modules into that context in a implementation-defined way. However, the module feature will initially be out of scope.
> Best Regards,
> Karthick Sankarachary

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.