rmiregistry on a different machine
posted 10 years ago
This is a bit of a confusing issue... the implementation of Registry provided by the default rmiregistry does throw AccessExceptions on any remote calls that will alter the services bound to the registry. However, there's nothing specific to RMI that would prevent doing a remote bind - you would just have to provide a Registry implementation that would allow it. I believe that the default Registry provided through rmiregistry did allow this at one time, but this was changed due to security concerns.... I think sometime around the JDK 1.3 - 1.4 releases.