jndi

JNDI spi impl for java namespace.

A simple implementation of JNDI. It is entirely library based, so no server instances are started, and it sits upon Java .properties files or XML files, so it is easy to use and simple to understand. The .properties/.xml files may be either on the file system or in the classpath.

The JNDI provider which launches the core and associated network services: Changepw, Kerberos, LDAP, and NTP if all are configured. By default only LDAP is configured to startup.

Simple JNDI with Bug Fixes

This feature enables the use of Java Naming and Directory Interface (JNDI) to access server configured resources such as DataSources or JMS Connection Factories. It also allows access to Java primitives configured in the server as a jndiEntry.

Contains a JNDI provider implementation which wraps the core so existing applications based on JNDI can use the server embedded transparently. Remote and local runtime operations will appear and feel exactly the same with a performance boost when local. All operations via this JNDI provider bypass the LDAP stack to perform ooerations directly on the ApacheDS core.

This feature contains the core bundles required by the JNDI feature

An in-memory implementation of JNDI, so no server instances are started. A java.util.Properties object, the structure of a root directory or a list of .property files serves as a model for the contexts structure. The contexts get populated with objects defined programmatically or declared in .properties, .xml or .ini files.

Provides some implementations of the specification JNDI.

This bundle contains the JNDI API