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 2012/06/25 15:45:42 UTC

[jira] [Resolved] (SLING-2511) Inactive class loader should still be usable

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

Carsten Ziegeler resolved SLING-2511.
-------------------------------------

    Resolution: Fixed
    
> Inactive class loader should still be usable
> --------------------------------------------
>
>                 Key: SLING-2511
>                 URL: https://issues.apache.org/jira/browse/SLING-2511
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR
>    Affects Versions: JCR Classloader 3.1.6
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: JCR Classloader 3.1.8
>
>
> A destroyed class loader should still be usable.
> For example otherwise we run into problems with the jsp scripting: The first request comes into the jsp scripting and starts compiling something and gets a jcr classloader (through the writer). While the compilation takes place, another request comes in to a different jsp which invalidates the first classloader as a jsp needs recompilation. The compilation of the first jsp now fails.
> If the classloader would still be usable, the compilation succeeds and the jsp is later on loaded with the fresh classloader anyway as the jsp scripting gets the latest classloader for loading jsps.

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