Friday, June 29, 2001 03:15 PM
I'm not sure if this will help. But you may wish to check the following a) that the RMI registry (if you're using it) on the server does not have the *_Stub in its classpath, b) that the *_Stub IS in the classpath of the class that registers (binds) the remote object with the registry, and c) that the same *_Stub is accessible via http: protocol for the client requesting it.
As per footnote on p. 63 of the J2EE in a Nutshell book (by O'Reilly), "Note that in order for the RMI registry to recognize and pass along the codebase property you specify, it has to be started in such a way that it can't find any of the remotely loaded classes on its CLASSPATH. So start your RMI registry with a CLASSPATH that doesn't include the stub/skeleton classes, etc., then run your RMI server with a CLASSPATH that includes all the required classes.