The JNDI is an API that provides a standard protocol for accessing and sharing any network resources and its file structure in internet/Intranet and supports accessing a variety of naming and directory services. The purpose of naming service is to associates names with objects and provides access to objects through mapping a unique id to each object and its name.
The ranges of objects in a naming system can from files in a file system and names located in Domain Name System records, to Enterprise JavaBeans components in an application server and user profiles in Lightweight Directory Access Protocol directory. If you want to use Java to write an application such as a network-enabled desktop, an application launcher, a search utility, a network management utility or anything that accesses objects in a naming system then JNDI is a good architecture for writing that application.
Architecture
The architecture of JNDI is like the JDBC architecture, in which both provide a standard protocol-independent API built on top of protocol-specific driver or provider implementations. It consists of the JNDI API and the JNDI SPI. The JNDI API allows Java applications to access a variety of naming and directory services. The JNDI SPI is designed to be used by arbitrary service providers including directory service providers. This enables a variety of directory and naming services to be plugged in transparently to the Java application which uses only the JNDI API.
The ranges of objects in a naming system can from files in a file system and names located in Domain Name System records, to Enterprise JavaBeans components in an application server and user profiles in Lightweight Directory Access Protocol directory. If you want to use Java to write an application such as a network-enabled desktop, an application launcher, a search utility, a network management utility or anything that accesses objects in a naming system then JNDI is a good architecture for writing that application.
Architecture
The architecture of JNDI is like the JDBC architecture, in which both provide a standard protocol-independent API built on top of protocol-specific driver or provider implementations. It consists of the JNDI API and the JNDI SPI. The JNDI API allows Java applications to access a variety of naming and directory services. The JNDI SPI is designed to be used by arbitrary service providers including directory service providers. This enables a variety of directory and naming services to be plugged in transparently to the Java application which uses only the JNDI API.
No comments:
Post a Comment