jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Klimetschek (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (JCR-2797) Xpath: pure descendant-or-self axis does not work
Date Thu, 21 Oct 2010 18:24:20 GMT

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

Alexander Klimetschek reopened JCR-2797:
----------------------------------------


Ok, I tested an expression like /content// in an Xpath tool (on an XML doc, see [1]), where
it worked.

Looking at it again, /jcr:root/content//node() should then do what I want. It is executed
in Jackrabbit, but does not return the /content node, only all nodes below.

[1] http://www.whitebeam.org/library/guide/TechNotes/xpathtestbed.rhtm using the expression
/parent/pet//

> Xpath: pure descendant-or-self axis does not work
> -------------------------------------------------
>
>                 Key: JCR-2797
>                 URL: https://issues.apache.org/jira/browse/JCR-2797
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core, xpath
>            Reporter: Alexander Klimetschek
>
> A pure descendant-or-self axis "//" does not work, albeit it is defined in JCR 1.0, section
6.6.4.6. Running this query
> /jcr:root/content//
> returns an error:
> Encountered "$" at line 1, column 38. Was expecting one of: "or" ... "and" ... "div"
... "idiv" ... "mod" ... "*" ... "return" ... "to" ... "where" ... "intersect" ... "union"
... "except" ... ... ... "/" ... "//" ... "=" ... "is" ... "!=" ... "<=" ... "<<"
... ">=" ... ">>" ... "eq" ... "ne" ... "gt" ... "ge" ... "lt" ... "le" ... "<"
... ">" ... "-" ... "+" ... "|" ... "[" ... ... ... ... ... "," ... ... ... for statement:
for $v in /jcr:root/content// return $v
> It only works in combination with another location step, like /jcr:root/content//* or
/jcr:root/content//test. Tested this on a 2.2 snapshot, but I think it was actually never
supported so far.
> The use case comes up when searching for a property in a subtree of a certain node, where
you want to include a property on that node directly as well, eg. /jcr:root/content//[@my:prop
= 'value']

-- 
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