[ http://jira.jboss.com/jira/browse/JBREM-42?page=comments#action_12315952 ] Tom Elrod commented on JBREM-42: ---------------------------------
Need to add API in the ServerInvocationHandler to get the classloader the handler wishes the server invoker to use for classloading. This is already available from the client side. This should resolve problems with loading context specific classes and will fall to the handler to be responsible for providing the correct classloader (or ruturn null if just wants to use the default). > two phase deserialization - handler classloading > ------------------------------------------------ > > Key: JBREM-42 > URL: http://jira.jboss.com/jira/browse/JBREM-42 > Project: JBoss Remoting > Type: Task > Components: general > Versions: 1.0.1 beta > Reporter: Tom Elrod > Assignee: Tom Elrod > Fix For: 1.2.0 beta > > > The payload is currently deserialized on the server side (ServerInvoker). > Need to only deserialize the remoting specific payload in the ServerInvoker > and pass along the still marshaled target payload to the sub-system handler > (UnifiedInvoker), since should have the same classloader context as the end > target. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
