| javax.naming.spi |
|
Provides the means for dynamically plugging in support for accessing
naming and directory services through the javax.naming
and related packages.
This package defines the service provider interface (SPI) of the Java Naming
and Directory InterfaceTM (JNDI).
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 SPI provides the means for creating JNDI service providers,
through which JNDI applications access different naming and
directory services.
Plug-in Architecture
The service provider package allows different implementations to be plugged in
dynamically.
These different implementations include those for the
initial context,
and implementations for contexts that can be reached
from the initial context.
Java Object Support
The service provider package provides support
for implementors of the
javax.naming.Context.lookup()
method and related methods to return Java objects that are natural
and intuitive for the Java programmer.
For example, when looking up a printer name from the directory,
it is natural for you to expect to get
back a printer object on which to operate.
Multiple Naming Systems (Federation)
JNDI operations allow applications to supply names that span multiple
naming systems. So in the process of completing
an operation, one service provider might need to interact
with another service provider, for example, to pass on
the operation to be continued in the next naming system.
The service provider package provides support for
different providers to cooperate to complete JNDI operations.
Package Specification
The JNDI SPI Specification and related documents can be found in the
JNDI documentation.
@since 1.3
|
| Java Source File Name | Type | Comment |
| ContinuationContext.java | Class | This class is for dealing with federations/continuations. |
| ContinuationDirContext.java | Class | This class is the continuation context for invoking DirContext methods. |
| DirectoryManager.java | Class | This class contains methods for supporting DirContext
implementations.
This class is an extension of NamingManager. |
| DirObjectFactory.java | Interface | This interface represents a factory for creating an object given
an object and attributes about the object.
The JNDI framework allows for object implementations to
be loaded in dynamically via object factories. |
| DirStateFactory.java | Interface | This interface represents a factory for obtaining the state of an
object and corresponding attributes for binding.
The JNDI framework allows for object implementations to
be loaded in dynamically via object factories.
A DirStateFactory extends StateFactory
by allowing an Attributes instance
to be supplied to and be returned by the getStateToBind() method.
DirStateFactory implementations are intended to be used by
DirContext service providers.
When a caller binds an object using DirContext.bind(),
he might also specify a set of attributes to be bound with the object.
The object and attributes to be bound are passed to
the getStateToBind() method of a factory. |
| InitialContextFactory.java | Interface | This interface represents a factory that creates an initial context.
The JNDI framework allows for different initial context implementations
to be specified at runtime. |
| InitialContextFactoryBuilder.java | Interface | This interface represents a builder that creates initial context factories.
The JNDI framework allows for different initial context implementations
to be specified at runtime. |
| NamingManager.java | Class | This class contains methods for creating context objects
and objects referred to by location information in the naming
or directory service.
This class cannot be instantiated. |
| ObjectFactory.java | Interface | This interface represents a factory for creating an object.
The JNDI framework allows for object implementations to
be loaded in dynamically via object factories.
For example, when looking up a printer bound in the name space,
if the print service binds printer names to References, the printer
Reference could be used to create a printer object, so that
the caller of lookup can directly operate on the printer object
after the lookup. |
| ObjectFactoryBuilder.java | Interface | This interface represents a builder that creates object factories.
The JNDI framework allows for object implementations to
be loaded in dynamically via object factories.
For example, when looking up a printer bound in the name space,
if the print service binds printer names to References, the printer
Reference could be used to create a printer object, so that
the caller of lookup can directly operate on the printer object
after the lookup. |
| Resolver.java | Interface | This interface represents an "intermediate context" for name resolution.
The Resolver interface contains methods that are implemented by contexts
that do not support subtypes of Context, but which can act as
intermediate contexts for resolution purposes.
A Name parameter passed to any method is owned
by the caller. |
| ResolveResult.java | Class | This class represents the result of resolution of a name.
It contains the object to which name was resolved, and the portion
of the name that has not been resolved.
A ResolveResult instance is not synchronized against concurrent
multithreaded access. |
| StateFactory.java | Interface | This interface represents a factory for obtaining the state of an
object for binding.
The JNDI framework allows for object implementations to
be loaded in dynamically via object factories.
For example, when looking up a printer bound in the name space,
if the print service binds printer names to References, the printer
Reference could be used to create a printer object, so that
the caller of lookup can directly operate on the printer object
after the lookup. |