[
https://issues.apache.org/jira/browse/SLING-5158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14963225#comment-14963225
]
Carsten Ziegeler commented on SLING-5158:
-----------------------------------------
The patch is large :) so rather than going through it line by linem could you
please elaborate a little bit on how the old ResourceProvider/Factory services
are handled?
In addition how is the following handle:
- 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?
> 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)
