[jboss-jira] [JBoss JIRA] (JBMESSAGING-1909) ClassNotFoundException when consuming a message with EJB handle inside an isolated EAR.

[Yong Hao Gao (Updated) (JIRA)]

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

Yong Hao Gao updated JBMESSAGING-1909:
--------------------------------------

        Fix Version/s: 1.4.0.SP3.CP15
                       1.4.8.SP6
                           (was: Unscheduled)
             Assignee: Yong Hao Gao
    Affects Version/s: 1.4.8.SP5
                       1.4.0.SP3.CP14

    
> ClassNotFoundException when consuming a message with EJB handle inside an isolated EAR.
> ---------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1909
>                 URL: https://issues.jboss.org/browse/JBMESSAGING-1909
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0.SP3.CP14, 1.4.8.SP1, 1.4.8.SP5
>            Reporter: David Stephan
>            Assignee: Yong Hao Gao
>             Fix For: 1.4.0.SP3.CP15, 1.4.8.SP6
>
>         Attachments: HandleEAR.ear
>
>
> When trying to pass the handle of an EJB3 bean which has been exposed with EJB2.1 client adapters, to an MDB. The handle is sent in an Object Message payload.
> The MDB then just gets the handle from the object message to get a hold of the Stateful bean.
> This works ok as long as the EAR, which packages all the beans and interfaces in a single EJB, is not isolated. If the EAR is isolated, the interface class cannot be found in the globalCache, and as the classloader being used is jboss-service.xml (obtained from ObjectInputStream.lastUserDefinedLoader()) the interface is blackListed, so it's not found here either.
> ObjectInputStreamWithClassLoader overrides resolveClass(), however in this scenario resolveProxyClass() is used and should also be overridden.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira