Hi, i have a weird problem, which probably could be a bug. I have several (entity) beans deployed in orion and a client, which retrieves the home interface of one of these and then creates new instances. Executed remote (on a different machine) the client behaves as expected. Executed on localhost, the client crashes with a class cast exception - the recieved home interface is of another type than expected. I inspected the returned objects prior of casting them to anything - and really, the local client (who's code is identical) recieves a home object for another bean than the requested. The derivation tree is as follows (the classes in parenthesis are implemented interfaces) __Proxy0 ( de.netmedia.ejb.base.binarybean.NMejbBinaryHome com.evermind.server.ejb.EntityContainer com.evermind.server.rmi.EvermindRemote ) com.evermind.reflect.Proxy ( ) java.lang.Object ( ) for the local case and __Proxy0 ( de.netmedia.ejb.base.treebean.NMejbTreeHome com.evermind.server.ejb.EntityContainer com.evermind.server.rmi.EvermindRemote ) com.evermind.reflect.Proxy ( ) java.lang.Object ( ) for the remote case. This happens without restarting the server - it really returns different classes. I wonder, if there can be any differences between the two cases - have you made some optimizations in the local case? I also wonder, how the server is able to have two fifferent versions of __Proxy0 with the same name within the same JVM.... Regards, Jens Stutte ____________________________________________ [EMAIL PROTECTED], http://www.netmedia.de NetMedia GmbH Neugrabenweg 5-7 66123 Saarbruecken Germany fon: +49 (0) 681 - 3 79 88 - 0 fax: +49 (0) 681 -�3 79 88 - 99
