You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Radu Cotescu (JIRA)" <ji...@apache.org> on 2014/03/27 10:55:15 UTC

[jira] [Updated] (SLING-3464) The DynamicClassLoaderManager doesn't reload classes when a bundle transitions from STARTED to RESOLVED

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

Radu Cotescu updated SLING-3464:
--------------------------------

    Description: 
The bundle activator from org.apache.sling.commons.classloader also acts as a SynchronousBundleListener, taking care to clean the DynamicClassLoaderManager (DCLM) when a bundle changes its state.

However, the DCLM doesn't get cleaned when a bundle transitions from ACTIVE to RESOLVED, which is inconsistent: for example no services will be resolved from that bundle, however classes already loaded through DCLM will get solved.

  was:
The bundle activator from org.apache.sling.commons.classloader also acts as a SynchronousBundleListener, taking care to clean the DynamicClassLoaderManager (DCLM) when a bundle changes its state.

However, the DCLM doesn't get cleaned when a bundle transitions from STARTED to RESOLVED, which is inconsistent: for example no services will be resolved from that bundle, however classes already loaded through DCLM will get solved.


> The DynamicClassLoaderManager doesn't reload classes when a bundle transitions from STARTED to RESOLVED
> -------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-3464
>                 URL: https://issues.apache.org/jira/browse/SLING-3464
>             Project: Sling
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: Commons ClassLoader 1.3.0
>            Reporter: Radu Cotescu
>             Fix For: Commons ClassLoader 1.3.2
>
>
> The bundle activator from org.apache.sling.commons.classloader also acts as a SynchronousBundleListener, taking care to clean the DynamicClassLoaderManager (DCLM) when a bundle changes its state.
> However, the DCLM doesn't get cleaned when a bundle transitions from ACTIVE to RESOLVED, which is inconsistent: for example no services will be resolved from that bundle, however classes already loaded through DCLM will get solved.



--
This message was sent by Atlassian JIRA
(v6.2#6252)