[ 
https://issues.apache.org/jira/browse/SLING-2447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238756#comment-13238756
 ] 

Carsten Ziegeler commented on SLING-2447:
-----------------------------------------

Creating a new session is pretty fast and should add no real overhead - and 
even if, classes are loaded usually only once and therefore it wouldn't even 
matter if creating a new session would decrease the class loading a little bit. 
In addition, compared to class generation and compilation this can be neglected 
anyway.
                
> ClassLoaderWriter should provide class loader for loading written 
> classes/resources
> -----------------------------------------------------------------------------------
>
>                 Key: SLING-2447
>                 URL: https://issues.apache.org/jira/browse/SLING-2447
>             Project: Sling
>          Issue Type: New Feature
>          Components: Commons, JCR, Scripting
>    Affects Versions: Scripting JSP 2.0.20, Scripting Java 2.0.2, JCR 
> Classloader 3.1.4, Commons Compiler 2.0.2, Commons ClassLoader 1.2.4
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Scripting JSP 2.0.22, Scripting Java 2.0.4, JCR 
> Classloader 3.1.6, Commons Compiler 2.0.4, Commons ClassLoader 1.2.6
>
>
> As a follow up to SLING-2445 the ClassLoaderWriter should be enhanced to 
> return a class loader which can be used to load the dynamically loaded 
> classes written through this writer.
> This writer should use the dynamic class loader as a parent and implement the 
> DynamicClassLoader interface which allows to check if the class loader is 
> still current.
> The returned classloader should not be cached by clients, they should just 
> get the class loader each time they require one. The writer ensures that 
> always a fresh loader is returned.
> The java and jsp scripting should use this class loader instead.

--
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

        

Reply via email to