[
https://issues.apache.org/jira/browse/SLING-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-1636.
-------------------------------------
Resolution: Fixed
Added a new interface DynamicClassLoader in revision 983910 which can be
implemented by dynamic class loaders. This allows clients to check the used
classloaders.
> Provide a mechanism to detect if a dynamic classloader is still valid
> ---------------------------------------------------------------------
>
> Key: SLING-1636
> URL: https://issues.apache.org/jira/browse/SLING-1636
> Project: Sling
> Issue Type: New Feature
> Components: Commons
> Affects Versions: Commons ClassLoader 1.1.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Commons ClassLoader 1.2.0
>
>
> In some situations it is useful to know if a used classloader is still
> live/valid. Especially with dynamic class loaders it happens that a
> classloader gets invalidated but is still in use. In such cases the client of
> such a classloader should be able to detect this and reload classes.
> One use case is scripting in Sling: we have the JCR based classloader and for
> example compiled scripts. A JCR classloader gets invalid as soon as something
> changes with the classes it has loaded in the repository. In this case the
> jsp script engine should reload the compiled classes
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.