[
https://issues.apache.org/jira/browse/SLING-5158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14964952#comment-14964952
]
Tomek Rękawek commented on SLING-5158:
--------------------------------------
So, the most up-to-date answer for the question about {{/foo}} provider which
fails to authenticates during {{getResource(/foo/bar)}} is that {{null}} will
be returned (so basically each provider _owns root_ by default). If some
provider wants to use the parent provider, it can do it too.
For the legacy providers, the adapter implementation checks the {{ownsRoot}}
property. If it's set to true and the current provider doesn't return anything,
the {{ResolveContext#parentProvider}} will be used. It should provide behaviour
compatible with the old API.
> 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)
