[
https://issues.apache.org/jira/browse/SLING-5158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14963263#comment-14963263
]
Tomek Rękawek commented on SLING-5158:
--------------------------------------
And for the case
{quote}
a new resource provider is mounted at /foo and it requires authentication.
However, authentication fails for the current user. There is another resource
provider at / which the user sucessfully authenticates to. What happens for a
getResource("/foo/bla") call?
{quote}
The user will get an exception. It will be {{LoginException}} during the
resource resolver creation, if the /foo provider is {{required}} or
{{SlingException}} during the {{getResource()}} invocation if the provider is
{{lazy}}.
This is just the current state, I'm not saying it should stay this way. If I
read your comment correctly, the failing provider should be ignored and the /
provider should be used - is that right?
> 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)
