We are currently working on upgrading Jackrabbit from 1.6.5 to 2.4.2 on our system. we run into problems in some XPath queries that worked great on version 1.6.5, and now it throws a javax.jcr.query.InvalidQueryException in 2.4.2. Did Jackrabbit change the way it analyzes XPath queries?
request:
//programs//*[child::*/@sunday]
in version 1.6.5 returns:
0 nodes returned in 1ms
and on 2.4.2 it returns:
null for statement: for $v in //programs//*[child::*/@sunday] return $v
source share