[
https://issues.apache.org/jira/browse/SLING-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17440451#comment-17440451
]
Carsten Ziegeler commented on SLING-2783:
-----------------------------------------
[~Henry Kuijpers] All resource providers need to be listed to guarantee a
correct result from a resource tree perspective. I think in the past the
thinking was that there are not many resource providers overlapping, especially
not for scripts. And in the end resource providers for each servlet are somehow
a special case.
Today, it is much easier to provide scripts out of bundles.
Therefore, there is since some time an option on the servlets resolver to
disable registering servlets as resource provider (for compatibility it is
enabled by default). Disabling this, makes the problem go away (and should have
no other negativ impact)
> 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
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: JCR Resource 2.7.0
>
>
> 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 was sent by Atlassian Jira
(v8.20.1#820001)
