[
https://issues.apache.org/jira/browse/SLING-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949105#comment-13949105
]
Carsten Ziegeler commented on SLING-3464:
-----------------------------------------
I guess, you mean from ACTIVE to RESOLVED.
The package admin class loader only loads classes when the bundle is ACTIVE -
this is to avoid the problem, that the interface class is already available
(jsp for example compiles fine) but the service is not.
Therefore, when a bundle goes back into the RESOLVED state, we should handle
this
> 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)
