compact3

Package javax.naming

提供用于访问命名服务的类和接口。

See: 描述

接口摘要

接口	描述
Context	该接口表示一个命名上下文，它由一组名称对对象绑定组成。
Name	该 Name接口表示一个通用的名字-一个有序的组件序列。
NameParser	此接口用于从分层命名空间中解析名称。
NamingEnumeration<T>	此接口用于枚举javax.naming和javax.naming.directory包中的方法返回的列表。
Referenceable	该接口由可以为其自身提供引用的对象实现。

类摘要

类	描述
BinaryRefAddr	该类表示通信端点的地址的二进制形式。
Binding	此类表示在上下文中找到的名称对对象绑定。
CompositeName	此类表示组合名称 - 跨多个命名空间的组件名称序列。
CompoundName	该类表示复合名称 - 来自分层名称空间的名称。
InitialContext	这个类是执行命名操作的起始上下文。
LinkRef	此类表示一个引用，其内容是名称，称为链接名称，该名称绑定到上下文中的原子名称。
NameClassPair	此类表示在上下文中找到的绑定的对象名称和类名称对。
RefAddr	该类表示通信端点的地址。
Reference	此类表示对在命名/目录系统外部找到的对象的引用。
StringRefAddr	此类表示通信端点的地址的字符串形式。

异常摘要

异常	描述
AuthenticationException	访问命名或目录服务时发生身份验证错误时抛出此异常。
AuthenticationNotSupportedException	当不支持所请求的身份验证的特定风格时，会抛出此异常。
CannotProceedException	抛出此异常以指示操作达到操作无法继续进行的名称中的一个点。
CommunicationException	当客户端无法与目录或命名服务通信时，抛出此异常。
ConfigurationException	出现配置问题时抛出此异常。
ContextNotEmptyException	尝试销毁不为空的上下文时抛出此异常。
InsufficientResourcesException	当资源不可用来完成请求的操作时，抛出此异常。
InterruptedNamingException	正在调用的命名操作已被中断时抛出此异常。
InvalidNameException	此异常表示指定的名称不符合命名系统的命名语法。
LimitExceededException	当方法由于用户或系统指定的限制而异常终止时，会抛出此异常。
LinkException	此异常用于描述解决链接时遇到的问题。
LinkLoopException	当检测到循环将尝试解析链接时，抛出此异常，或已达到链接计数的实现特定限制。
MalformedLinkException	当解决或构建链接时遇到格式错误的链接时抛出此异常。
NameAlreadyBoundException	通过方法抛出此异常，表示无法添加绑定，因为该名称已被绑定到另一个对象。
NameNotFoundException	当名称的组件由于未绑定而无法解析时抛出此异常。
NamingException	这是Context和DirContext接口中的操作抛出的所有异常的超类。
NamingSecurityException	这是Context和DirContext接口中的操作抛出的与安全相关异常的超类。
NoInitialContextException	当不能创建初始上下文实现时，抛出此异常。
NoPermissionException	尝试执行客户端没有权限的操作时抛出此异常。
NotContextException	当命名操作进行到需要上下文以继续操作的点时抛出此异常，但解析的对象不是上下文。
OperationNotSupportedException	当上下文实现不支持正在调用的操作时，抛出此异常。
PartialResultException	抛出此异常以指示到目前为止返回或返回的结果是部分的，并且该操作无法完成。
ReferralException	此抽象类用于表示引用异常，该引用异常是响应于LDAP v3服务器返回的 引用而生成的。
ServiceUnavailableException	尝试与目录或命名服务通信并且该服务不可用时，会抛出此异常。
SizeLimitExceededException	当方法产生超过大小相关限制的结果时，抛出此异常。
TimeLimitExceededException	当方法不在指定的时间限制内终止时，抛出此异常。

Package javax.naming Description

Provides the classes and interfaces for accessing naming services.

This package defines the naming operations of the Java Naming and Directory Interface^TM (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.

Context

This package defines the notion of a context, represented by the Context interface. A context consists of a set of name-to-object bindings. Context is the core interface for looking up, binding, unbinding, and renaming objects, and for 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, Name can be used to represent a composite name (CompositeName) so that you can name an object using a name which spans multiple namespaces.

The overloads that accept Name are useful for applications that need to manipulate names: composing them, comparing components, and so on. 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

The Binding class represents a name-to-object binding. It is a tuple containing the name of the bound object, the name of the object's class, and the object itself.

The Binding class is actually a subclass of NameClassPair, which consists simply of the object's name and the object's class name. The NameClassPair is useful when you only want information about the object's class and do not want to pay the extra cost of getting the object.

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. JNDI defines a reference, represented by the Reference class, which contains information on how to construct a copy of the object. 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 JNDI, all naming and directory operations are performed relative to a context. There are no absolute roots. Therefore 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

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.

Package Specification

The JNDI API Specification and related documents can be found in the JNDI documentation.

从以下版本开始：

1.3