A special jar file that contains a pre-loaded partition with schema
information. This schema partition will mount off of the ou=schema
namingContext. This artifact contains the db files for this partition.
It must be used with the apacheds-bootstrap-extract jar which contains
the classes to install these files.
This plugin pre-loads a set of schema objects into a special fixed schema
partition within the server. It uses the bootstrap schema objects to do
this at build time. The schema partition files created are then packaged
using the jar plugin to become what is known as the bootstrap partition jar.
Server's core contains the JNDI provider, interceptors, schema, and
database subsystems. The core is the heart of the server without protocols
enabled.
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.
A JDBM entry store which does not have any dependency on core interfaces.
The JDBM partition will use this store and build on it to adapt this to
server specific partition interfaces.
Having this separate module without dependencies on core interfaces makes
it easier to avoid cyclic dependencies between modules. This is especially
important for use within the bootstrap plugin which needs to build the
schema partition used for bootstrapping the server.
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.
Several kinds of two column key/value data structures, in memory and on
disk which sort keys can can be used to implement xdbm partitions. JDBM
is one example. These partition use the same database structure or scheme
for maintaining LDAP entries and facilitating search operations on them.
This module contains common tools that could be used to manage aspects
common to all xdbm implementations.