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 is a bug.
it actually is expected behaviour.
Note: the following works: //[EMAIL PROTECTED]:created = true()].
that's exactly where you can use the true() and false(). to check if a boolean property is true or false.
regards marcel
