jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Radu Ana-Maria <radu.a...@gmail.com>
Subject Re: indexing configuration
Date Fri, 11 Sep 2009 15:08:02 GMT
10x for the reply but i found the solution! my parent property node
@versionDoc = 'da'  was not indexed..
 initialy i thought that this configuration property was read from tables
database but, i found that it isn't like this!

ana


On Fri, Sep 11, 2009 at 5:29 PM, Marcel Reutegger
<marcel.reutegger@gmx.net>wrote:

> Hi,
>
> On Wed, Sep 9, 2009 at 10:14, Radu Ana-Maria <radu.anna@gmail.com> wrote:
> > i have some questions:
> > 1. since the condition for ancestor can be write :*/ for the parent can
> be
> > write as well yes?
>
> yes, that's possible as well.
>
> >      - because i write something like this:
> >                       <index-rule nodeType="th:plainDocument"
> > condition="parent::*/@versionDoc = 'da' ">
> >                       </index-rule>
> >         and all the nodes of type plainDocument  are still indexing even
> if
> > are children of a node that have property <<versionDoc = 'da'>> am i
> missing
> > something in my code?
>
> that looks correct. can you please post the complete configuration
> together with the node type definitions that you have? thanks.
>
> > 2. can i make a condition that referes a parent of a parent :
> >                      <index-rule nodeType="th:plainDocument"
> > condition="parent::*/*/@versionDoc = 'da' ">
> >                       </index-rule> (the node's are still indexed ..this
> > code is ignored)
> >         is this a correct code? if not, can i do this in an other way?
> how?
>
> that's not possible. you cannot use multiple slashes in a condition.
>
> regards
>  marcel
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message