ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tammo van Lessen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (ODE-150) XPath10 in transition condition uses wrong context node
Date Wed, 01 Aug 2007 12:19:52 GMT

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

Tammo van Lessen resolved ODE-150.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1

fixed in #561373.

> XPath10 in transition condition uses wrong context node
> -------------------------------------------------------
>
>                 Key: ODE-150
>                 URL: https://issues.apache.org/jira/browse/ODE-150
>             Project: ODE
>          Issue Type: Bug
>            Reporter: Tammo van Lessen
>            Assignee: Tammo van Lessen
>            Priority: Critical
>             Fix For: 1.1
>
>
> 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

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


Mime
View raw message