JNDI, the Java Naming and Directory Interface, is a fundamental component of J2EE (Java 2 Platform, Enterprise Edition) and any J2EE application. However, since JNDI does not depend on any other J2EE technologies, and the JNDI client interfaces are part of the J2SE (Java 2 Platform, Standard Edition) distribution, J2SE applications can also exploit JNDI's benefits. In this article, Brian Goetz explores basic JNDI concepts, how JNDI is commonly used, and how to configure a free JNDI provider for use with J2SE applications. (1,600 words; April 19, 2002)
2. Use JNDI to share objects between different virtual machines
Imagine the following: Process A on machine B puts an object into a Hashtable. Now, a separate process C on a different machine D can access that object from its own local copy of the Hashtable -- even after process A terminates and the virtual machine unloads! Now imagine all this is achieved without the use of RMI, and without involving an ORB, CORBA, EJB, or a database. What's the secret? The Java Naming and Directory Interface (JNDI). This month's tool is the JNDIHashtable -- which, as its name reveals, uses JNDI to do its thing. (2,600 words)
3. JNDI overview, Part 1: An introduction to naming services
If a distributed application's components can't locate one another, then they can't work together. Therefore, distributed applications require, almost by definition, something to help the components to find each other. The Java Naming and Directory Interface (JNDI) provides just this capability. This month, Todd Sundsted ventures into the relatively uncharted waters of this important, but often overlooked, Java technology. (1,900 words)
4. JNDI overview, Part 2: An introduction to directory services
As applications become more distributed, the efficient management and distribution of the information upon which they depend becomes more and more of a problem. Directory services such as LDAP (the Lightweight Directory Access Protocol) address this problem. For Java applications, the Java Naming and Directory Interface (JNDI) provides a generic interface to LDAP and other directory services. This month, Todd Sundsted introduces you to JNDI directory services. (1,300 words)
A JNDI service can be much more than a computerized card catalog. JNDI's object-storage capabilities allow it to play the role of resource administrator in your distributed applications and to provide simple, manageable object persistence. In recognition of its potential, the architects of key Java technologies such as JDBC and EJB built JNDI into their specifications. This month Todd Sundsted shows you how to store objects in a JNDI service. (1,900 words)
6. JNDI overview, Part 4: the Doc-u-Matic, a JNDI application
You've read each lesson and learned the material -- now it's time to play. In order to demonstrate clearly the strength of JNDI, Todd Sundsted takes you on a tour of Doc-u-Matic, a JNDI-enabled document publication and distribution infrastructure. You'll see how a naming and directory service, combined with JNDI's ability to store Java objects, leads to simpler -- yet more powerful -- distributed applications. (1,600 words)
