No, I have tracked these down and the problems were due to Class.forName caching old classes as the vm level in a ClassLoader to class name map. They have been fixed by either not allowing calls to Class.forName using alternate implementation of MarshalledObject, or by ensuring that the lookup is in the context of a unique ClassLoader.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Jung , Dr. Christoph" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 27, 2002 12:40 AM Subject: AW: [JBoss-dev] Class.forName() problem Hi, ... Furthermore, I suspect the forName0 natives to do weird things with in-VM class caching (otherwise they could have easily delegated ClassLoader.loadClass(className,true) or such). I once had some test code that showed that after cycling some classloaders alltogether, you were still able to get references to "old" classes/classloaders from the new classes/classloaders. Aren�t there still some ClassCastExceptions appearing here and there which nobody can yet explain? _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
