You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2015/10/02 18:14:27 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14941322#comment-14941322 ] 

Konrad Windszus commented on SLING-5087:
----------------------------------------

As creating exceptions is expensive I would prefer being able to switch it off (for production servers).

> 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)