[ http://issues.apache.org/jira/browse/JCR-246?page=all ]
Jukka Zitting resolved JCR-246:
-------------------------------
Fix Version: (was: 1.0)
Resolution: Won't Fix
Assign To: Jukka Zitting
The JSR 170 actually only specifies the current node and optionally a property
of the current node as permitted scopes for the jcr:contains function.Thus the
proposed feature would be a Jackrabbit-specific extension.
A standard compliant implementation of the
"//page[jcr:contains(paragraph,'foo')]" query would be
"//page[paragraph[jcr:contains(.,'foo')]]". This however does not work in
Jackrabbit until JCR-247 gets resolved.
Marking this issue "Won't Fix" for now. Please reopen if JSR 283 or another JCR
revision broadens the scope of the jcr:contains function. Before that the
solution to the described problem pends on the resolution of JCR-247.
> Child node support for jcr:contains()
> -------------------------------------
>
> Key: JCR-246
> URL: http://issues.apache.org/jira/browse/JCR-246
> Project: Jackrabbit
> Type: Improvement
> Components: xpath
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
>
> The jcr:contains() full text query function only supports querying the
> properties of the current node. It would be nice to add support for child
> nodes so that queries like "//page[jcr:contains(paragraph, 'foo')]" would be
> possible.
> See http://thread.gmane.org/gmane.comp.apache.jackrabbit.devel/3889 for
> Christophe Lombart's question about this feature.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
