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 2015/02/02 09:08:35 UTC

[jira] [Closed] (SLING-4363) Unregistering a resource provider should also reregister the resource resolver factory

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

Carsten Ziegeler closed SLING-4363.
-----------------------------------

> Unregistering a resource provider should also reregister the resource resolver factory
> --------------------------------------------------------------------------------------
>
>                 Key: SLING-4363
>                 URL: https://issues.apache.org/jira/browse/SLING-4363
>             Project: Sling
>          Issue Type: Improvement
>          Components: ResourceResolver
>    Affects Versions: Resource Resolver 1.1.10
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Resource Resolver 1.1.12
>
>
> Right now, only if a resource provider factory is unregistered, the resource resolver factory is reregistered. This is in order to notify all clients which potentially have used an instance of the provider factory and restart them.
> However, if a client holds resources from an unregistered resource provider, this might result in a memory leak as well, therefore we should use the same mechanism and reregister the resource provider factory



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