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/06/15 10:53:00 UTC

[jira] [Resolved] (SLING-4803) Improve logging in case the DynamicClassLoaderManagerFactory is reloaded

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

Konrad Windszus resolved SLING-4803.
------------------------------------
       Resolution: Fixed
    Fix Version/s: Commons ClassLoader 1.3.4

Committed in rev. 1685514.

> Improve logging in case the DynamicClassLoaderManagerFactory is reloaded
> ------------------------------------------------------------------------
>
>                 Key: SLING-4803
>                 URL: https://issues.apache.org/jira/browse/SLING-4803
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>             Fix For: Commons ClassLoader 1.3.4
>
>         Attachments: SLING-4803-v01.diff
>
>
> For certain bundle events the DynamicClassLoaderManagerFactory is reregistered (https://github.com/apache/sling/blob/trunk/bundles/commons/classloader/src/main/java/org/apache/sling/commons/classloader/impl/Activator.java#L123). It would be good to provide logging why the DynamicClassLoaderManagerFactory has been reregistered in that case.



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