ODE
  1. ODE
  2. ODE-150

XPath10 in transition condition uses wrong context node

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.1
    • Component/s: None
    • Labels:
      None

      Description

      Hi,

      when using XPath 1.0 expressions with variable references in transition conditions (may also occur in assigns), the evaluation starts on the part's (first) child node. AFAIK XPaths on variable refs should behave like XPaths on documents, i.e. the evaluation should start on virtual root element which has the content of the selected part as child.

      Assume the variable "myVar" has part 'request' with the following content (in my case it is defined by a messageType whose part is defined by a complexType):
      <packageName>Gold</packageName>

      According to the BPEL 2.0 spec, the expression

      $myVar.request/packageName = 'Gold' should be evaluated to true.

      But it currently does not. A working expression is $myVar.request/self::packageName = 'Gold', but this is IMHO not compliant to the spec.

      I might be wrong, but I'm pretty sure that there is something wrong with Ode's JaxenContext. IMHO when retrieving variables content node, it should be nested in to a wrapper element before passing it to jaxen.

      Cheers,
      Tammo

        Activity

        Hide
        Tammo van Lessen added a comment -

        fixed in #561373.

        Show
        Tammo van Lessen added a comment - fixed in #561373.

          People

          • Assignee:
            Tammo van Lessen
            Reporter:
            Tammo van Lessen
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development