Well, the java.rmi.Naming is used to bind name with a registry. I only have the experience with rmiregistry application. It should use the rmi native protocol to store/retrieve information to/from the registry.
The context is designed to provide an common interface for different Directory services. For example you can use LDAP as your naming service.
You have the ability to swith to another kind of directory service almost with out impact on your code.
If you are in a
J2EE environment, normally you would use JNDI. When you are in J2EE environment , what you have is not only the Remote interface,
but also a lot of other information for example user information ... Most of the companies use directory services to provide those kind of information. You cannot use Naming to access those information. In the system except EJB, you also have to bind DataSource, JMS , etc.... Those should be managed by JNDI.
It is convenient for the administrator to admin the system when a directory service is used. On the other hand the rmiregistry is just
a simple program. Only the remote inteface can be bind with it. The user can only query it by name. It is possible weblogic has a better implementation which allows the admin to do more stuff on it compare to the sun implementation.
That is my 2 cents
Lin