Hi, On Mon, Sep 28, 2009 at 23:54, Michael Shoener <[email protected]> wrote: > I tried your suggestion to use @jcr:data and still get nothing.
see: http://jackrabbit.apache.org/frequently-asked-questions.html "Why doesn't //*[jcr:contains(@jcr:data, 'foo')] return matches for binary content?" > What exactly does the "." in the jcr:contains search in relation to the > node? it means that the XPath context node is searched using the jcr:contains() function. In jackrabbit jcr:contains will search all properties on that node unless otherwise configured in the indexing configuration. see: http://wiki.apache.org/jackrabbit/IndexingConfiguration > Any other suggestions? you could separate the resource from the file. e.g. have the description property on a node that is distinct from the node where you have the jcr:data on. using built in node types that would be: //element(*, nt:file)[jcr:contains(jcr:content, 'example')] or if you also want to search on description: //element(*, nt:file)[jcr:contains(@description, 'example' or jcr:contains(jcr:content, 'example')] (assuming you have a custom node type that extends from nt:file and allows you to set @description) regards marcel
