[
https://issues.apache.org/jira/browse/SLING-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598700#comment-13598700
]
Carsten Ziegeler commented on SLING-2783:
-----------------------------------------
Ok, forget about the example /libs :) it was a bad choice...
It's possible to mount resource providers at any path, these shadow potential
resources from the JCR. That's a fairly common scenario. In those case we have
to filter, otherwise you get a resource from a search and try to get the same
resource from the resource resolver using the path and you get something
different. Returning something which is actually not in the resource tree is
wrong and might create very hard to trace problems.
> Search implementation does not respect resource providers
> ---------------------------------------------------------
>
> Key: SLING-2783
> URL: https://issues.apache.org/jira/browse/SLING-2783
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Resource 2.2.4
> Reporter: Carsten Ziegeler
> Fix For: JCR Resource 2.2.6
>
>
> If a search is performed by the JCR Resource Provider the returned set is not
> checked whether these resources/nodes are accessible through the resource
> tree.
> For example a different resource provider might be mounted at /libs -
> therefore all results for this sub tree need to be discarded.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
