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

2014-03-20 Thread Radu Cotescu
Hi,

Could someone please take a look at this and confirm if we're talking about
a bug or a feature?

Thanks,
Radu

On Wednesday, March 19, 2014, Radu Cotescu (JIRA) j...@apache.org wrote:

 Radu Cotescu created SLING-3464:
 ---

  Summary: 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
 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.



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



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

2014-03-19 Thread Radu Cotescu (JIRA)
Radu Cotescu created SLING-3464:
---

 Summary: 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 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.



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