The information on these pages may be out of date, or may refer to
resources that have moved or have been made read-only.
For more information please refer to the Apache Attic
|Initial version||Vasily Zakharov, Nadya Morozova: document created.||March 23, 2006|
|Formatting update||Nadya Morozova: document created.||September 21, 2006|
|Linking update||Sveta Konovalova: incorporating in website, removing disclaimer.||March 2007|
The target audience for the document includes a wide community of engineers interested in using the RMI registry in their JNDI applications and in further work with the product to contribute to its development. The document assumes that readers are familiar with RMI, JNDI and the Java programming language.
This document uses the unified conventions for the DRL documentation kit.
The RMI registry context, based on a registry location, and the RMI Registry Service Provider allow JNDI applications to access remote objects bound in the RMI registry, as described in the Java* RMI Specification .
The provider supplies JNDI with the same essential functionality as
java.rmi.Naming class does.
The DRL RMI Service Provider is an independent implementation of the RMI Service Provider for JNDI. You can also consult additional information resources on RMI , RMI Service Provider  and JNDI in general .
The provider can store
javax.naming.Referenceable objects. The RMI registry context
and references to individual RMI objects can be bound into other JNDI contexts.
The DRL provider does not support binding other contexts into the RMI registry,
so that you cannot address objects in this context using composite name requests
through the registry.
In addition to the general properties , the DRL RMI Registry Provider uses the following JNDI environment properties:
Specifies the RMI registry service provider class name as the
initial context factory to be used by the
Use this property with the
property, which specifies the location of the RMI registry
for the usage of the initial context. Otherwise, the initial
context you created can only resolve complete RMI URLs.
java.rmi.server.RMIClientSocketFactoryinterface. The instance of this class is passed to the
The URL context factory,
enables passing RMI URLs as names to the JNDI initial context.
and provides converting registry references into the corresponding registry
contexts or remote objects.
 RMI Specification, http://java.sun.com/j2se/1.5.0/docs/guide/rmi/spec/rmiTOC.html
 Sun's RMI Provider, http://java.sun.com/j2se/1.5.0/docs/guide/jndi/jndi-rmi.html
* Other brands and names are the property of their respective owners.