The terminology in NJCL and JNDI may be familiar to you, but some terms are used in different ways. To ensure that you have a good understanding of NJCL and JNDI, a list of key terms with their defined uses is presented here. In some cases, links are included to more detailed discussions in other Concepts topics.
The indivisible component of an object name. For further information, see Section 1.7, Object Names.
Information associated with a directory object. An attribute consists of a type identifier and a set of attribute values. For a more complete description, see Section 1.11, Attribute Concepts.
The association or mapping of an atomic name with an object. For a more complete discussion of binding, see Context Binding.
A name that spans multiple naming systems.
The process of resolving a name that spans multiple naming systems.
The arrangement of namespaces from autonomous naming systems to form one logical namespace. Sometimes referred to as a federated namespace.
A name in the namespace of a single naming system. It is a sequence of zero or more atomic names composed according to the naming convention of that naming system. For a detailed discussion of the different types of names, see Object Names.
An object whose state is a set of bindings with distinct atomic names. See Clarifying Contexts for more detailed information on the uses of context.
A specialization of an object factory that accepts information about how to create a context, such as a reference, and returns an instance of the context.
A network database of hierarchical sets of objects.
An object that is stored in the directory, which contains name and attribute information. Sometimes referred to as a directory entry.
Provides operations for creating, adding, removing, and modifying the attributes associated with objects in a directory.
Configuration parameters used to customize the operation of an object or service provider.
An aggregate of autonomous naming systems that cooperate to support name resolution of composite names through a standard interface. Each member of the federation has autonomy in its choice of operations and naming conventions. A federated naming service provides operations on a federated naming system.
A binding between a context in one naming system and an object in another naming system. For a more detailed discussion, see Context Federation in the Clarifying Contexts section.
The starting point for resolution of names in naming and directory operations. For a more detailed description, see Initial Context in the Clarifying Contexts section.
A human-friendly identifier for identifying an object or a reference to an object. For a discussion of the different types of names, see Object Names.
The process of resolving a name to the object to which it is bound. See Context Binding for more information on name resolution.
A set of all the names in a naming system or instance of a name system.
The set of syntactic rules that govern how a name is generated. These rules determine whether a name is valid or invalid in the context in which the name is used.
Provides the operations on a naming system. For more detailed information, see Naming System Concepts.
A connected set of contexts of the same type (having the same naming convention). For more detailed information, see Section 1.9, Naming System Concepts.
A producer of objects that accepts some information about how to create an object, such as a reference, and then returns an instance of that object.
Represents an object that exists outside the naming system. JNDI attempts to convert the reference into the object that it represents before returning it to the client.
Specifies the types of objects a directory may contain, and the mandatory and optional attributes that directory objects of different types are to have. It may also specify the structure of the namespace and the relationship between different types of objects. For a more detailed discussion, see Schema Concepts.
A logical expression specifying the attributes that the directory objects being requested should have and be used by the directory to locate those objects.
An implementation of a context or initial context that can be plugged in dynamically to the JNDI architecture to be used by an application. For a more detailed discussion, see Service Provider Concepts.
A context that is bound in another context of the same type (having the same naming convention).