Hello, > > To clarify the situation: I have a node with the path a/b/c > in the XPath query result, node c can be accessed, but a and > b cannot. But the node c will then also be removed from the > result list, because the document order cannot be created > because of its unauthorized ancestors. So I have the > situation that node c will be removed from the result > although is is an authorized and accessible node, only its > ancestors are not.
Think is part of *how* you implemented the AccessManager I think. > > Which version of Jackrabbit are you using? First of all, for > > JackRabbit > >> 1.5 the default setting for respectDocumentOrder will be > false. For < > > 1.5 it is true. You can configure it to false/true by adding > > > > <param name="respectDocumentOrder" value="false"/> > > > > To you <SearchIndex> element in repository.xml > > I use Jackrabbit 1.4. I implemented the solution the > Sébastien suggested, adding a "order by @jcr:score" to the > query. Works very well for me. Perfect. Ard > > Regards and Thanks, > > Jan > > >
