Agreed. This issue can be fixed by redesigning the protocol. Mixing classloaders in a request object sounds strange to me, too. On the other hand, I'd like to know if there will be any potential issues with implementing R1/R2 transport for R3 regarding this issue. We still have to deal with mixed classloaders in the compatibility layer I guess? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169180#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...