If skeletons for remote objects are loaded via the RMIClassLoader (using the property java.rmi.server.codebase to locate the skeletons), an exception will be thrown if the remote object implementation to which the skeleton dispatches makes an RMI call. The RMISecurityManager restricts classes loaded by it from connecting to any host.

Requiring that stubs be loaded by the RMIClassLoader via "codebase" and that skeletons be loaded via CLASSPATH make server configuration more complex. Both scenarios should be supported where stubs.