Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Enterprise-level applications use a lot of different directory services-lookup services that locate re-
sources associated with a particular name. When you use RMI, for example, you locate objects with
a directory service called the RMI Registry. When you use CORBA, you use the COS Naming fa-
cility (CORBA's naming service) to locate objects. When you convert a hostname to an IP address,
you usually use a directory service called DNS (Domain Name Service). There are also general dir-
ectory services that use protocols, such as X.500 (the CCITT directory standard) and LDAP (Light-
weight Directory Access Protocol). These directory services can hold many kinds of data.
Although most people tend to use the terms "naming service" and "directory service" interchange-
ably, there is a difference. A naming service associates a single name with a specific resource. A dir-
ectory service associates a name with a set of attributes and resources. When you search a naming
service, you can only search for a specific name. When you search a directory, you can search for
items matching a specific set of attributes.
One of the interesting things about all these types of naming and directory services is that they gen-
erally perform the same task-mapping a name to some set of attributes or objects. Of course, not all
directory services are created equally. Some of them have a flat namespace, whereas others offer a
tree structure for the names. Some of them allow you to store specific types of objects, whereas oth-
ers allow you to store almost any kind of object.
The Java Naming and Directory Interface (JNDI) draws a distinction between naming services and
directory services. A naming service maps a name to an object. The RMI Registry and the CORBA
Naming Service are both examples of naming services. You can only store an RMI object in the
RMI Registry and you can only store a CORBA object in the CORBA Naming Service. A directory
service also stores objects, but these objects can have associated attributes that the directory service
recognizes. You can search a directory using the item attributes. For example, you can search an
LDAP directory for everyone in a specific department or everyone named Smith.
JNDI provides a uniform way to access naming and directory services. It supports flat namespaces
as well as tree namespaces, and it allows you to store many different types of objects. The beauty of
JNDI lies it its simplicity and uniformity. After you know the basic JNDI API calls, you can read
data out of any kind of directory as long as there is a JNDI service provider for that directory.
You have already encountered JNDI in several earlier chapters. You use JNDI to locate Enterprise
JavaBeans and JDBC connection pools from within your EJB container. You might have implemen-
ted simple lookup schemes before in your applications; that is, you create a class with static lookup
methods or store a Hashtable in a static field somewhere. You might choose to use JNDI to replace
these kinds of local storage mechanisms, although you might need to write your own service pro-
vider.
JNDI is also extremely useful in the area of configuration. If many applications use common con-
figuration data, you might consider storing the data in a directory service, such as LDAP, instead of
in a file or database. LDAP is especially good if the configuration information is hierarchical-that is,
if it is more like a tree structure than a flat list of values.
One of the hidden benefits of directory services is the fact that there are a lot of directory service
browsers and editors-especially for LDAP. You can view the contents of the directory and edit them
using an off-the-shelf tool. That saves you from having to write a custom configuration editor.
Note
Don't worry about setting defining the class for the initial context factory unless you get an error
telling you there's no initial context factory.
When you run your program, you can specify the initial context factory on the command-line using
the -D option:
java -Djava.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory
usingj2ee.naming.JNDIDemo
You can also specify the initial context factory in a Hashtable that you can pass to the InitialContext
constructor:
java Djava.naming.factory.initial=weblogic.jndi.WLInitialContextFact-
ory
-Djava.naming.provider.url=t3://localhost:7001 MyTestClient
When you develop Enterprise Java Beans, you can usually count on the environment being set up
properly ahead of time, so you normally don't need to initialize any properties or set any system
properties. When you run your client programs to test the EJBs, however, you usually need to spe-
cify an initial context factory.
Although most people use the InitialContext object as their first entry point into JNDI, there is an
alternative. You can use the javax.naming.spi.NamingManager class to create a service-specific
context for you based on a URL prefix. A fully qualified JNDI name is of the form service://item-
name, where service is a name such as iiop, rmi, ldap, and so on, and itemname is the name of the
item in that service. The NamingManager class lets you create a Context object based on the service
name. For example, to create an LDAP Context object, you can call:
Object ob = context.lookup("ldap://localhost/dc=wutka,dc=com");
The InitialContext object knows how to resolve references that use other kinds of services. If you
try this with a context returned by getURLContext, however, you'll get an error telling you that the
name isn't valid for the context you are using.
Okay, now that you have a Context object, you can use the lookup method to locate an object. For
example, when you locate an EJB, you usually make a call like this:
ctx.bind("rmi://localhost/MyRemoteObject", remoteObject);
If the object already exists in the directory, bind throws a NameAlreadyBoundException. The re-
bind method does the same thing as bind except that it doesn't care whether the object already ex-
ists:
ctx.rebind("rmi://localhost/MyRemoteObject", remoteObject);
rebind doesn't throw an exception if the object doesn't exist; that is, you can use rebind to create a
new association as well as to overwrite an old one.
ctx.unbind("rmi://localhost/MyRemoteObject");
Make sure each EJB client creates its own InitialContext, especially if you are using EJB security
credentials. The credentials are tied to the InitialContext, and if you aren't careful, one client may be
using another client's credentials. Normally this isn't a problem if the clients are running as separate
processes. If you're writing a Web application, however, on a server that acts as multiple clients, you
must be careful to keep the contexts separated.
Directory Operations
JNDI has directory-specific extensions for performing directory operations as opposed to the simple
name-value operations in most naming services. The DirContext interface and InitialDirContext
classes provide additional methods for dealing with directories. The directory-specific classes are
all contained within the javax.naming.directory package.
If you need to perform directory operations, create an InitialDirContext instead of an InitialContext.
For example
import javax.naming.*;
import javax.naming.directory.*;
while (e.hasMoreElements())
{
// Get the next attribute
Attribute attr = (Attribute) e.nextElement();
Due to possible network changes, you may not be able to access http://ldap.wutka.com in the future.
You might need to set up your own LDAP server to run the example.
country top c
organization top o
organizationalUnit top ou
The LDAP specification also lists some common attribute names. These attribute names tend to
look confusing at first glance because many of them are only one or two characters long. You see
these attributes in other places too, such as in X.509 certificates (for digital signatures and encryp-
tion). One of the reasons for the similarity is that LDAP uses many of the items defined in the
X.500 series of recommendations (standards), which includes X.509.
Table 18.2 lists some of the common attributes and their meanings.
st State or province
o Organization
ou Organizational unit
One other concept you should be aware of is that a context is really a set of names. You can create a
context that is a subset of names by calling createSubcontext in the DirContext object. Essentially, a
subcontext is just the set of names starting at a particular node in the directory tree.
The interesting thing is, you create a new node in the tree by creating a new subcontext. Listing
18.2 shows a program that adds two entries to the LDAP directory. Notice that the program must
supply a username in the form of a SECURITY_PRINCIPAL and a password in the form of SE-
CURITY_CREDENTIALS to make changes to the LDAP directory. Most servers let you read the
directory anonymously but require a username and password to make changes.
import java.util.*;
import javax.naming.*;
import javax.naming.directory.*;
import javax.naming.*;
import javax.naming.directory.*;
searchAttrs.put("sn", "Tippin");
import javax.naming.*;
import javax.naming.directory.*;
NamingEnumeration e = attrs.getAll();