[jboss-jira] [JBoss JIRA] (AS7-5652) POJO subsytem isn't setting the TCCL to the application's class loader

James Livingston (JIRA) jira-events at lists.jboss.org
Mon Nov 19 22:11:21 EST 2012


     [ https://issues.jboss.org/browse/AS7-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Livingston reopened AS7-5652:
-----------------------------------



This is marked as resolved and the github PR closed as merged, but the change is not in AS7 master and the git history indicates it was never committed. Perhaps the merge was a accidentally not pushed to the github repo?
                
> POJO subsytem isn't setting the TCCL to the application's class loader
> ----------------------------------------------------------------------
>
>                 Key: AS7-5652
>                 URL: https://issues.jboss.org/browse/AS7-5652
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: POJO
>    Affects Versions: 7.1.1.Final, 7.1.3.Final (EAP)
>         Environment: AS7 upstream master
>            Reporter: Michael Vetter
>            Assignee: Ales Justin
>             Fix For: 7.2.0.Alpha1
>
>
> The POJO subsytem isn't setting the TCCL (Thread.currentThread().getContextClassLoader()) to the application's class loader while invoking on the application's lifecycle methods. The TCCL is set to the "ModuleClassLoader for Module "org.jboss.as.pojo:main" from local module loader".
> It was working in JBoss5.1 to start a bean with an xml file (<deployment xmlns="urn:jboss:bean-deployer:2.0"> ...) and to use the TCCL during deployment to load resources and classes from the ear. With the pojo ModuleClassLoader these resources are not found.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-jira mailing list