Java Naming and Directory Interface (JNDI) is a standard Java interface for accessing distributed objects and services by name. It provides a portable, unified interface for naming and directory services. The JNDI specification is independent of any specific directory or naming service such as LDAP, NDS, DCE/CDS, or NIS.
EAServer’s JNDI implementation includes the JNDI service provider interface (SPI), which enables you to use a variety of custom directory and naming services. EAServer uses the SPI in conjunction with the CosNaming interface to provide component lookup capability. Given a bound name, the SPI locates the referenced package and component. Once it locates the component, the SPI works with the client stub interface to instantiate the component and return the requested object.
For complete information about instantiating and resolving objects with JNDI, see Chapter 12, “Creating CORBA Java Clients,” in the EAServer Programmer’s Guide.
When you start the server, the JNDI classes required
for the server’s JDK version are configured automatically.
