Jndi (Java naming and directory Interface,java naming and directory interface) is a standard Java naming system interface provided by Sun, and Jndi provides a unified client API, Through the implementation of a different access provider Interface Jndi Service Provisioning Interface (SPI), the manager maps the Jndi API to a specific naming service and directory system, allowing Java applications to interact with these naming services and directory services. The directory service is a natural extension of the naming service. The key difference between the two is that the object in the directory service can have a name and attributes (for example, the user has an email address), and the object in the naming service has no attributes[1]. The cluster Jndi implements high reliability Jndi, which ensures the load balance and error recovery of Jndi through the server cluster. In a globally shared manner, an application server in the cluster guarantees the independence of the local Jndi tree and has a global jndi tree. Each application server binds the deployed service object to its own local jndi tree, and also binds to a shared global Jndi tree, which implements global Jndi and its own jndi connections. JNDI (Java naming and directory Interface) is an application-designed API that provides developers with a common, unified interface for locating and accessing various naming and directory services, similar to JDBC, which is built on the abstraction layer. Now that Jndi has become one of the standards of the Java EE, all the Java EE containers must provide a JNDI service. The existing directories and services that JNDI can access are: DNS, Xnam, Novell Directory Services, LDAP (Lightweight Directory Access Protocol Lightweight Directory Access Protocol), CORBA Object Services, file systems, Windows Xp/2000/nt/me/9x registry, RMI, DSML v1&v2, NIS.
JNDI (Java naming and directory Interface,java naming and directory interfaces)
