[
https://issues.apache.org/jira/browse/SLING-5158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14963468#comment-14963468
]
Carsten Ziegeler commented on SLING-5158:
-----------------------------------------
Yes, correct - basically this is what we had in the first ResourceProvider with
the ownsRoot property. The advantage here is, for every path only a single
resource provider is asked to return the resource. If that returns null, we're
done.
The implementation of the resource provider might call the parent resource
resolver, e.g. the /foo resource provider might decide to call the root
resource provider (through the ResolveContext).
> Refactor ResourceResolver to use the new ResourceProvider API
> -------------------------------------------------------------
>
> Key: SLING-5158
> URL: https://issues.apache.org/jira/browse/SLING-5158
> Project: Sling
> Issue Type: Sub-task
> Components: ResourceResolver
> Reporter: Tomek Rękawek
> Fix For: Resource Resolver 1.2.8
>
> Attachments: SLING-5158.patch
>
>
> Change the Resource Resolver implementation to use the new ResourceProvider
> interface and create a bridge service to support the old providers and
> factories as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
