You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2016/07/25 22:23:20 UTC

[jira] [Closed] (SLING-5885) ResourceResolverFactory might not get correctly re-registered if configuration is changed

     [ https://issues.apache.org/jira/browse/SLING-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-5885.
-----------------------------------

> ResourceResolverFactory might not get correctly re-registered if configuration is changed
> -----------------------------------------------------------------------------------------
>
>                 Key: SLING-5885
>                 URL: https://issues.apache.org/jira/browse/SLING-5885
>             Project: Sling
>          Issue Type: Bug
>          Components: ResourceResolver
>    Affects Versions: Resource Resolver 1.4.12, Resource Resolver 1.4.14
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Resource Resolver 1.4.16
>
>
> If the resource resolver factory gets reregistered, the old instance is not correctly removed which then in turn is used by components. But it will return null for the resource resolver factory service as it is deactivated. Therefore the system becomes useless



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)