[
https://issues.apache.org/jira/browse/SLING-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598810#comment-13598810
]
Carsten Ziegeler commented on SLING-2783:
-----------------------------------------
This is the default setup: the jcr provider is mounted at /, all other
providers are mounted at some paths, ootb these are bundle resource providers
and the servlet provider. So as soon as you search for something which is
hidden by them, you hit the problem.
But even more problematic, we have many users using the file system provider
and mounting stuff at some points.
It is way too easy to say this is a wrong setup, we have the resource
abstraction with the way the providers work and we should stick to this theme
and implement everything correctly.
And I don't think that this has a huge performance impact as the check should
be pretty fast. This is a bug which needs to be fixed anyway.
> 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
