You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2009/07/14 13:49:15 UTC
[jira] Created: (SLING-1046) Use commons classloader instead of
dynamic import *
Use commons classloader instead of dynamic import *
---------------------------------------------------
Key: SLING-1046
URL: https://issues.apache.org/jira/browse/SLING-1046
Project: Sling
Issue Type: Improvement
Components: Event
Affects Versions: Extensions Event 2.0.4
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: Extensions Event 2.0.6
The new commons class loader provides a better handling of loading dynamic classes than the dynamic import *
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1046) Use commons classloader instead of
dynamic import *
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-1046.
-----------------------------------
Resolution: Fixed
Instead of using dynamic import package *, the event module now uses the commons classloader to dynamically load classes. Changed in revision: 794169
> Use commons classloader instead of dynamic import *
> ---------------------------------------------------
>
> Key: SLING-1046
> URL: https://issues.apache.org/jira/browse/SLING-1046
> Project: Sling
> Issue Type: Improvement
> Components: Event
> Affects Versions: Extensions Event 2.0.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 2.0.6
>
>
> The new commons class loader provides a better handling of loading dynamic classes than the dynamic import *
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.