[jboss-remoting-issues] [JBoss JIRA] Updated: (JBREM-1019) RemotingClassLoader needs option to delegate to user class loader before parent

[Scott M Stark (JIRA)]

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

Scott M Stark updated JBREM-1019:
---------------------------------

    Attachment: JBREM-1019.patch


With the attached patch, I can set the -Dorg.jboss.remoting.classloadingParentFirstDelegation=false property and the user class loader handles the class loading of the transport unmarshalling.

> RemotingClassLoader needs option to delegate to user class loader before parent
> -------------------------------------------------------------------------------
>
>                 Key: JBREM-1019
>                 URL: https://jira.jboss.org/jira/browse/JBREM-1019
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.GA (Pinto)
>            Reporter: Scott M Stark
>            Assignee: Ron Sigal
>             Fix For: 2.4.0.SP1
>
>         Attachments: JBREM-1019.patch
>
>
> For the jbossas5 app client container, a class loader policy that loads from the child first is used to pickup the client jar manifest references. If such a class loader is registered as the user class loader with the RemotingClassLoader, its not going be delegated to first. This results in duplicate and conflicting classes being loaded.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira