>> 6. property conditions with deep property paths should be supported as well >- if the underlying provider supports it. so .property() could optionally >> accept a path to a deeper property. to clarify in javadocs. > >I'm not sure if we should go there, so your use case is searching for a >resource which has a child resource that has a property foo=bar (or >something like that)?
yes - this is supported by xpath query currently, and - at least in jackrabbit 2 - it was performant if it matches with a proper lucene index configuration for the search index that includes a certain level of child nodes. i looked in some of our old projects as well and found this usecase in some places. stefan
