JBoss Remoting unmarshalls the entire request before it dispatches the request. A big problem with this is when you are dispatching to a different, non-default, classloader domain in that the parameter classes may not be available during demarshalling and class not found exceptions (or CCE when the dispatch actually gets to the target object) will happen. My bet is that our IIOP layer right now has this problem as well.
The solution would be to not demarshall the method arguments and have invocation.getArguments do a callback to the remoting layer for a demarshall. I don't think this is possible to implement for any IIOP solution or any solution that automatically unmarshalls the buffer. Maybe I am missing something, but these class loading boundaries are a real flaw in the whole Invoker architecture. Bill View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833753#3833753 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833753 ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
