[
https://issues.apache.org/jira/browse/SLING-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-2445.
-----------------------------------
> Deprecate DynamicClassLoaderProvider
> ------------------------------------
>
> Key: SLING-2445
> URL: https://issues.apache.org/jira/browse/SLING-2445
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Affects Versions: Commons ClassLoader 1.2.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Commons ClassLoader 1.3.0
>
>
> The concept of the DynamicClassLoaderProvider - while looking attractive -
> doesn't work the way it has been intended. The major reason for this
> interface was dynamic class loading for the scripting support. However we can
> do this in a much cleaner way through the ClassLoaderWriter (separate issues
> will follow). A dynamic class loader provider has no way to tell the dynamic
> class loader manager, that it is not current anymore and a new instance needs
> to be created. Maybe we could come up with a clever way of doing this, but in
> the end the effort is not worth it as there is no other usage for this
> concept than scripting.
> In addition, it opens a door for circumventing the OSGi class loading
> completely and that's another good reason to forget about this.
> The idea is to:
> a) deprecate the interface
> b) do not call these providers anymore
> c) log a warning if a provider is found
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira