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/01/31 19:37:39 UTC
[jira] [Comment Edited] (SLING-5470) Resource providers might not
be closed
[ https://issues.apache.org/jira/browse/SLING-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125448#comment-15125448 ]
Carsten Ziegeler edited comment on SLING-5470 at 1/31/16 6:36 PM:
------------------------------------------------------------------
The ResourceResolverContext should not hold a reference to the ResourceResolver - same is true for the components referenced by the ResourceResolverContext
was (Author: cziegeler):
The ResourceResolverContext should not hold a reference to the ResourceResolver
> Resource providers might not be closed
> --------------------------------------
>
> Key: SLING-5470
> URL: https://issues.apache.org/jira/browse/SLING-5470
> Project: Sling
> Issue Type: Bug
> Components: ResourceResolver
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.3.0
>
>
> The CommonResourceResolverFactoryImpl contains some code to make sure that all resource resolvers (and therefore the providers) are closed - as soon as there is no reference to them anymore
> With the refactoring to the new provider API, this functionality has been removed - while the resource resolver context is still closed, the providers are not closed (logged out)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)