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 (Commented) (JIRA)" <ji...@apache.org> on 2012/03/16 09:15:49 UTC
[jira] [Commented] (SLING-2438) Class might never be loaded if the
bundle is in state resolved on the first attempt
[ https://issues.apache.org/jira/browse/SLING-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230967#comment-13230967 ]
Carsten Ziegeler commented on SLING-2438:
-----------------------------------------
I've committed a first version together with a test case in revision 1301365.
I'll leave this bug open for further tests
> Class might never be loaded if the bundle is in state resolved on the first attempt
> -----------------------------------------------------------------------------------
>
> Key: SLING-2438
> URL: https://issues.apache.org/jira/browse/SLING-2438
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons ClassLoader 1.2.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Commons ClassLoader 1.2.6
>
>
> If a class from a resolved bundle is tried to be loaded, it is not loaded but rather be put into the negative cache (see SLING-2232)
> However, the check to reregister the classloader is done for a bundle resolved event, therefore the classloader is not reregistered once the bundle is started and the class could be loaded
--
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