Print-friendly Version   Download Documentation

The Java Naming and Directory Interface (JNDI) provides naming and directory functionality to applications written in the Java programming language. It is designed to be independent of any specific naming or directory service implementation. Thus a variety of services--new, emerging, and already deployed ones--can be accessed in a common way.

The JNDI architecture consists of an API (Application Programming Interface) and an SPI (Service Provider Interface). Java applications use this API to access a variety of naming and directory services. The SPI enables a variety of naming and directory services to be plugged in transparently, allowing the Java application using the API of the JNDI technology to access their services.

Enhancements in Java SE 6

For enhancements for all recent JNDI versions, see Enhancements.

API and SPI Specification

• JNDI API and SPI Specification - A list of the packages included in the JNDI technology.

Tutorials

• JNDI Tutorial - A tutorial introduction to the JNDI technology with programming examples.

API Enhancements

• See Java™ JNDI Enhancements

More Information

• The JNDI Home Page
• Subscribe to the JNDI-INTEREST list
• See a demonstration namespace browser written using JNDI and Swing
• Related documents
• JNDI Architecture Documents:
  • JNDI API - also available in PDF
  • JNDI SPI - also available in PDF
  
  
• JNDI Service Providers:
  To use JNDI with a particular naming or directory service, you need a JNDI service provider, which is a module that plugs in beneath the JNDI API to access the naming or directory service. The JNDI web site maintains a list of service providers available for JNDI.
  
  Java 2 SDK, v 1.4 and later releases include the following service providers:
  • The LDAP Service Provider
  • The COS Naming Service Provider
  • The RMI Registry Service Provider
  • The DNS Service Provider