When you started the RMIRegistry did it get the correct classpath to find
your _stub and _skel files? This message says no... The message is probably
very appropriate; it is saying that on the remote side of the RMI connection
(which would be the RMIRegistry) there was an unmarshalling excpetion, caused
by the classloader's inability to find Objeto_Stub.class. If you were relying
on picking up your classes via :.: in the classpath somewhere, then you can
fix this be specifying the actual path to your classes explictly. The
RMIRegistry may not be getting started from your CWD... I know it doesn't
on other unix platforms. Try something along the lines of...
cd project/classes/ #or where ever your classes are ...
setenv CLASSPATH `pwd`:$CLASSPATH #change based on your shell of choice
rmiregistry &
java Prueba
> java.rmi.ServerException: Server RemoteException; nested exception is:
> java.rmi.UnmarshalException: error unmarshalling arguments;
> nested exception is:
> java.lang.ClassNotFoundException: Objeto_Stub
