Adapter capabilities

The JNDI Adapter has the following capabilities:

  • A card or GET or PUT rule represents a JNDI operation. JNDI operations include lookup, add, modify or delete.
  • The adapter provides access to records and attributes that can be set in the map, assuming the underlying service provider supports add, modify and delete.
  • RDN modification, including renaming, is not supported. However, RDNs can be deleted and added in a modified state, assuming the service provider supports delete and add. An RDN is analogous to the name of the file in a hierarchical file system in Windows or UNIX.
  • Objects created in one card can be used as parameters to methods in subsequent calls. These objects must be created by invoking an operation that returns an object.
  • Reference labels identify objects. Objects that are returned from method calls are assigned a label by the adapter. The label is of the form Ref.nn, where nn is a number which uniquely identifies the object.
  • The return values of any of the methods can be returned from a GET call. The schemas provide a mechanism allowing the user to select which methods the return values should be provided for. These return values can be primitive types, for example, int, strings, arrays, or local or remote objects. In the case of remote objects, the reference label is returned so that the object can be used in a subsequent call.
  • Objects can be shared between the JNDI, JMS, and Java Class adapters.