[jboss-jira] [JBoss JIRA] (AS7-5718) Client deserialising objects using wrong classloader

[James Livingston (JIRA)]

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

James Livingston reopened AS7-5718:
-----------------------------------



Did you want to add the integration test for this? It's at https://github.com/jbossas/jboss-as/pull/3302 if you did, feel free to re-close the issue if it's okay without it. I hadn't submitted the PR previously because it would fail without the remote-naming fix.
                
> Client deserialising objects using wrong classloader
> ----------------------------------------------------
>
>                 Key: AS7-5718
>                 URL: https://issues.jboss.org/browse/AS7-5718
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Naming
>    Affects Versions: 7.1.3.Final (EAP)
>            Reporter: James Livingston
>            Assignee: James Livingston
>             Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
>
>
> The commands in org.jboss.naming.remote.protocol.v1.Protocol deserialize objects using the Unmarshaller from ReadUtil. That does not explicitly set a ClassResolver, so it defaults to using the TCCL. Since the handle*Message methods are run in a thread pool, the TCCL could be set to anything, so the commands need to ensure that the correct classloader (presumably the one calling the Context methods) is used.

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