[
https://issues.apache.org/jira/browse/SLING-12019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17766367#comment-17766367
]
Julian Sedding commented on SLING-12019:
----------------------------------------
Merged [PR
#104|https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/104].
> Avoid duplicate ResourceResolverFactory registrations
> -----------------------------------------------------
>
> Key: SLING-12019
> URL: https://issues.apache.org/jira/browse/SLING-12019
> Project: Sling
> Issue Type: Bug
> Components: ResourceResolver
> Affects Versions: Resource Resolver 1.10.0
> Reporter: Carsten Ziegeler
> Assignee: Julian Sedding
> Priority: Critical
> Fix For: Resource Resolver 1.11.0
>
>
> It seems that in some situations a new resource resolver factory is
> registered without unregistering the old one - which leads to two factories
> being registered. As not all components do eager service binding, these
> components stick to the old factory - and the old factory in turn is
> basically "empty" meaning all resource providers are unregistered. This
> prevents those components from reaching any resource, although everything
> looks fine.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
