Michael Dürig wrote:
The use case is the spec. AFAIK the query is valid XPath and JSR 170
explicitly requires support for true() and false().
from a mere syntactic standpoint that correct, but jackrabbit only supports
true() and false() in specific locations of a statement.
So I guess this
The use case is the spec. AFAIK the query is valid XPath and JSR 170
explicitly requires support for true() and false(). So I guess this is a
bug.
Note: the following works: //[EMAIL PROTECTED]:created = true()].
Michael
Alexander Klimetschek wrote:
What is the use-case for this query? JCR
What is the use-case for this query? JCR only supports a subset of
XPath, so it might be correct, that this query is not valid... the
true() predicate does not bring any new information anyway.
Regards,
Alex
On Thu, Jul 10, 2008 at 9:12 PM, MARTINEZ Antonio
<[EMAIL PROTECTED]> wrote:
> Hello,
>
>
Hello,
And according to the JSR170 document, it should work since the Boolean
function true() should just be a true expression.
Using this query returns all my "pon" objects
//Inventory//ne/rack/subrack/slot/pon
But using
//Inventory//ne/rack/subrack/slot/pon[true()]
I get error
"j
