This package
contains classes and interfaces for accessing naming
services.
Context
This package defines the notion of a
Context, which is the core interface for looking up, binding/unbinding,
renaming objects, and creating and destroying subcontexts.
lookup() is the most commonly used operation.
You supply lookup()
the name of the object you want
to look up, and it returns the object bound to that name.
For example, the following code fragment looks up
a printer and sends a document to the printer object
to be printed:
Printer printer = (Printer)ctx.lookup("treekiller");
printer.print(report);
Names
Every naming method in the Context
interface has two
overloads: one that accepts a
Name argument and one that accepts a string name.
Name is an interface that represents a generic
name--an ordered sequence of zero of more components.
For these methods, if the Name argument is an instance of
CompositeName, it represents a
composite name
so that you can name an object using a name which spans multiple namespaces.
If the Name argument is of any other type, it represents a
compound name.
(Names are covered in the
Beyond the Basics 
trail.)
The overloads that accept Name
are useful for applications that need to manipulate names: composing
them, comparing components, and so on.
If the name argument is a string, it represents a composite name.
The overloads that accept string names are likely to be more useful
for simple applications, such as those that simply read in a name
and look up the corresponding object.
Bindings
listBindings() returns an enumeration of name-to-object
bindings.
Each binding is represented by an instance of the
Binding class.
A binding is a tuple containing the name of the bound object,
the name of the object's class, and the object itself.
list() is similar to listBindings(),
except that it returns an enumeration of
NameClassPair.
NameClassPair contains an object's name and the name of
the object's class.
The list() method is useful for applications such
as browsers that wish to discover information about the objects
bound within a context, but don't need all of the actual objects.
Although listBindings() provides all of the same information,
it is potentially a much more expensive operation.
References
Objects are stored in naming and directory services in different ways.
If an object store supports storing Java objects,
it might support storing an object in its serialized form.
However, some naming and directory services do not support the
storing of Java objects. Furthermore, for some
objects in the directory, Java programs are but one group of applications
that access them. In this case, a serialized Java object might
not be the most appropriate representation.
Finally, a reference might be a very compact representation
of an object while its serialized form might contain a lot more state
(see
Naming Concepts 
).
The JNDI defines the
Reference class
to represent a reference.
A reference contains information on how to construct a copy of the object.
The JNDI will attempt to turn references looked up from the directory
into the Java objects they represent, so that
JNDI clients have the illusion that what
is stored in the directory are Java objects.
The Initial Context
In the JNDI, all naming and directory operations are performed relative
to a context. There are no absolute roots.
Therefore the JNDI defines an
initial context,
InitialContext, which provides a starting point for naming and directory operations.
Once you have an initial context, you can use it to
look up other contexts and objects.
Exceptions
The JNDI defines a class hierarchy for exceptions that can be thrown in
the course of performing naming and directory operations. The root of
this class hierarchy is
NamingException.
Programs interested in dealing with a particular exception
can catch the corresponding subclass of the exception.
Otherwise, programs should catch NamingException.
