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/10/03 07:22:26 UTC
[jira] [Reopened] (SLING-5087) The ResourceResolverImpl should
provide a stack trace when CRUD operations are performed with a closed
resolver
[ https://issues.apache.org/jira/browse/SLING-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler reopened SLING-5087:
-------------------------------------
I agree with Konrad, and I think the exception variable should be volatile (just to be on the safe side)
> The ResourceResolverImpl should provide a stack trace when CRUD operations are performed with a closed resolver
> ---------------------------------------------------------------------------------------------------------------
>
> Key: SLING-5087
> URL: https://issues.apache.org/jira/browse/SLING-5087
> Project: Sling
> Issue Type: Improvement
> Components: ResourceResolver
> Affects Versions: Resource Resolver 1.2.6
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Fix For: Resource Resolver 1.2.8
>
>
> Currently trying to use a closed resource resolver for CRUD operations will throw a {{java.lang.IllegalStateException}}. However, it would also be useful to log where the resolver was closed, to help debugging.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)