[
https://issues.apache.org/jira/browse/SLING-5158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14963277#comment-14963277
]
Carsten Ziegeler commented on SLING-5158:
-----------------------------------------
The LoginException for required is good, I think getResource() should just
return null. We should not mimic the old behaviour and fall back to another
provider. If we just return null, we finally get a consistent tree: either the
user gets the /foo/bla resource from the /foo provider or no resource. With the
old provider approach, a user might get the /foo/bla resource from the /foo
provider or a /foo/bla resource from the root provider or null
> 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)
