Marcel Reutegger wrote: > > JSR 170 does not specify how you can match the node name in a query. > except if > you know the name exactly: //my-node-name > > There already is an enhancement request filed in jira: > http://issues.apache.org/jira/browse/JCR-696 >
I've been wishing for this feature as well. But perhaps someone could shed some light on the underlying issue: Is it be better to represent a name you might search against as a property, or as a node name? Using properties has the advantages of not needing a different query function, and would avoid some of the character quoting complications. But then, node names become more like arbitrary ids, and paths become less readable. And perhaps there are also performance costs (at least, with respect to exact-name searches)? Cheers, Joshua -- View this message in context: http://www.nabble.com/searching-nodes-tf3058568.html#a8552125 Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
