Uploaded image for project: 'ODE'
  1. ODE
  2. ODE-411

Express Yourself - With XQuery



    • New Feature
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.2
    • 2.0
    • None
    • platform-independent


      This issue is a duplicate of ODE-369 to track the integration of XQuery into Ode 2.x (trunk)

      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


        1. xquery-support-for-trunk.txt
          106 kB
          Karthick Sankarachary

        Issue Links



              karthick Karthick Sankarachary
              karthick Karthick Sankarachary
              0 Vote for this issue
              0 Start watching this issue