The JNDI schema provides a standard set of APIs that are independent of the naming system, which are built on the drivers associated with the naming system. This layer helps separate the app from the actual data source, so regardless of whether the app accesses LDAP, RMI, DNS, or other directory services. In other words, Jndi is independent of the specific implementation of the directory service, and the directory can be used as long as there is a directory service Provider interface (or driver). An important point to note about Jndi is that it provides an application programming interface (application programming Interface,api) and a service provider Interface (services provider INTERFACE,SPI). The real implication of this is that in order for an app to interact with a naming service or directory service, there must be a Jndi service provider for the service, which is where the Jndi SPI works. A service provider is basically a set of classes that implement JNDI interfaces for a variety of specific naming and directory services-much like the JDBC driver implements the JDBC interface for a variety of specific database systems. As an application developer, we don't have to worry about the specific implementation of the Jndi SPI. You only need to confirm that each naming or directory service you want to use has a service provider.
The JNDI schema provides a standard set of APIs that are independent of the naming system
