15 messages in org.apache.jackrabbit.usersRe: OCM - Issue while loading list of...
FromSent OnAttachments
Kaizer ShaikhOct 30, 2007 8:03 am 
Christophe LombartOct 31, 2007 12:38 am 
Felix MeschbergerOct 31, 2007 12:50 am 
Kaizer ShaikhNov 5, 2007 10:56 pm 
KaizerNov 6, 2007 8:29 pm 
Marcel ReuteggerNov 7, 2007 1:29 am 
KaizerNov 7, 2007 9:00 pm 
Marcel ReuteggerNov 9, 2007 2:15 am 
KaizerNov 13, 2007 1:45 am 
Christophe LombartNov 13, 2007 12:12 pm 
KaizerNov 13, 2007 8:49 pm 
Christophe LombartNov 14, 2007 7:37 am 
Kaizer ShaikhNov 15, 2007 3:41 am 
Christophe LombartNov 15, 2007 4:43 am 
Kaizer ShaikhNov 21, 2007 3:33 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: OCM - Issue while loading list of classes at that path itself.Actions...
From:Marcel Reutegger (marc@gmx.net)
Date:Nov 7, 2007 1:29:18 am
List:org.apache.jackrabbit.users

Kaizer wrote:

I was trying to have a deeper look at this problem and found that its related to the way the jackrabbit QueryManager searches based on the jcrExpression. Suppose I've created two nodes "some/test" under the root node. Now, if i create a query like ("/jcr:root//some/test//element(*, "my:type")"), I dont get any results. If i create the query as ("/jcr:root//some//element(test, "my:type")"), it works fine. I had a look at the JCR spec and it says that the constraint for obtaining Descendants or self path is /jcr:root/some/nodes// element(*, my:type).

this is just the mandatory feature set, jackrabbit also allows you to use the descendant-or-self axis anywhere else in the path.

/jcr:root//some/test//element(*, my:type)

will not return results because you probably have no nodes under /some/test

also note that the first // is unnecessary in your case.

regards marcel