[jira] Resolved: (SLING-1191) Dynamic class loader providers are not reloaded when bundles are updated/installed etc.

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

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

Carsten Ziegeler resolved SLING-1191.
-------------------------------------

    Resolution: Fixed

Added a new method to the dynamic class loader provider. release(ClassLoader)
This method is invoked whenever the dynamic class loader is destroyed. This allows the provider to react on this situation and free any resources.
When a new dynamic class loader is created, a new class loader is request from the provider.

> Dynamic class loader providers are not reloaded when bundles are updated/installed etc.
> ---------------------------------------------------------------------------------------
>
>                 Key: SLING-1191
>                 URL: https://issues.apache.org/jira/browse/SLING-1191
>             Project: Sling
>          Issue Type: Bug
>          Components: Commons, JCR
>    Affects Versions: JCR Classloader 2.0.6, Commons ClassLoader 1.0.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: JCR Classloader 3.0.0, Commons ClassLoader 1.1.0
>
>
> While the dynamic class loader is unregistering itself and reregistering, if a bundle is updated that is used for class loading, the dynamic class loader providers are unaware of this.
> So while the new dynamic class loader is using the new classes, for example the jcr class loader provider still uses the old classes - which ends somewhere in a class cast exception

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.