Repository

Artifacts/Jars

Popular Tags

ajax analysis annotations ant apache api archetype aspect asynchronously beans binding bpm build buildsystem bytecode cache cms codecoverage codehaus collections concurrency container database directory distributed doc eclipse ejb esb format framework graph graphics hadoop hibernate html http ide imap io jbi jdbc jdo jini jms jmx jndi jsf jsp language logging mail maven metadata microsoft mock net osgi parser pdf persistence plugin pool portal portlet query regexp rmi rpc rss ruleengine scheduling scm scripting security server servlet soa soap socket spring ssh svg swt system taglib template testing transaction ui web webdav webframework webserver webservice workflow xml xquery xslt

[See All Tags]

Maven Repository: jndi

ldap-clients
Java LDAP Clients
directory-clients » ldap-clients

ApacheDS Main
A single executable server jar containing all dependencies. This jar can be used as the JNDI provider or to fire up the standalone directory server.
directory.directory » apacheds-main

ApacheDS Core
Server's core contains all backend subsystems. It depends on protocol and uses it with seda to service LDAP requests. The core contains the JNDI provider, interceptor framework, interceptor services, the schema subsystem and the database subsystem. Hence the core is the heart of the server.
directory.directory » apacheds-core

ApacheDS Shared
Created to eliminate cyclic project dependencies between the core and the maven plugin. Any code shared across modules in general can go here so long as it does not depend on other modules.
directory.directory » apacheds-shared

Apache Directory Project
The Apache Directory Server (ApacheDS) is an embeddable LDAPv3 directory server with other protocol plugins such as kerberos. It is designed to be completely pluggable in every aspect including backends and frontend handlers making making it an ideal experimentation platform for LDAP protocol testing, and for use in building other tools like like meta directories, and virtual directories. ApacheDS aims to introduces stored procedures, triggers, views, and queues to the world of LDAP.
directory.directory » apacheds

ApacheDS LDAP Provider
The protocol provider used to snap in LDAP handlers and codecs into the protocol framework. These handlers are JNDI clients, specifically LDAP JNDI callers. Any JNDI provider can be used for the provider but the primary target is the core's JNDI provider.
directory-protocols » ldap-protocol

Kerberos Protocol Provider
A protocol provider for Kerberos handlers and codecs.
directory-protocols » kerberos-protocol

Apache's ASN.1 based LDAP BER Message Provider
A provider for the LDAP message framework (in LDAP commons) based on the Apache ASN.1 BER Runtime.
directory-shared » apache-ldapber-provider

Common LDAP API
Common LDAP packages used for protocol compliant parsing of distinguished names, LDIFs, filters, and urls. Also contains the Common Message API which enables a plugable interface for ASN.1 BER Message codec providers.
directory-shared » ldap-common

Apache's new ASN.1 based LDAP BER Message Provider
A new provider for the LDAP message framework (in LDAP commons) based on the Apache ASN.1 BER Runtime.
directory-shared » apache-new-ldapber-provider

Kerberos Common
Common Kerberos 5 classes.
directory-shared » kerberos-common

ApacheDS Main
A single executable server jar containing all dependencies. This jar can be used as the JNDI provider or to fire up the standalone directory server.
directory » apacheds-main

ApacheDS Core
Server's core contains all backend subsystems. It depends on protocol and uses it with seda to service LDAP requests. The core contains the JNDI provider, interceptor framework, interceptor services, the schema subsystem and the database subsystem. Hence the core is the heart of the server.
directory » apacheds-core

ApacheDS Shared
Created to eliminate cyclic project dependencies between the core and the maven plugin. Any code shared across modules in general can go here so long as it does not depend on other modules.
directory » apacheds-shared

Apache Directory Project
The Apache Directory Server (ApacheDS) is an embeddable LDAPv3 directory server with other protocol plugins such as kerberos. It is designed to be completely pluggable in every aspect including backends and frontend handlers making making it an ideal experimentation platform for LDAP protocol testing, and for use in building other tools like like meta directories, and virtual directories. ApacheDS aims to introduces stored procedures, triggers, views, and queues to the world of LDAP.
directory » apacheds

ApacheDS Plugin
A collection of tools as plugins to manage various tasks associated with the directory server.
directory » maven-directory-plugin

simple-jndi
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.
simple-jndi » simple-jndi

LdapTemplate
Java framework to simplify LDAP operations, based on the pattern of Spring's JdbcTemplate. Relieves the users of the burden of looking up and closing contexts, looping through NamingEnumerations, encoding/decoding values and filters, and more.
net.sf.ldaptemplate » ldaptemplate

ASN.1 BER Runtime
API containing functionality used for encoding and decoding BER streams both in blocking and non-blocking modes.
directory-asn1 » asn1-ber

ASN1 Stub Compiler
An ASN1 stub compiler that generates POJOs and their encoders/decoders that work within the snickers framework.
directory-asn1 » stub-compiler

ASN.1 DER Runtime
API containing functionality used for encoding and decoding DER streams in blocking mode. This is stepping-stone code meant to facilitate the migration of Kerberos, which was developed outside of the ASF, to the Apache Directory project's ASN.1 Runtime.
directory-asn1 » asn1-der

Apache ASN.1
The ASN.1 subproject attempts to isolate the ASN.1 libraries and tools for encoding ASN.1 in BER/DER/CER/PER encodings. The LDAP and X.500 aspects of the directory project impose the need for ASN.1 and BER codecs. Kerberos requires DER. Rather than implement highly specific and britle code for these needs we decided to separate out the APIs and implementations used for dealing with ASN.1 codecs for any ASN.1 defined protocol.
directory-asn1 » asn1

ASN.1 new BER Runtime
A new BER implementation
directory-asn1 » asn1-new-ber

Stateful chunking codec API for ASN.1 runtime
API for stackable stateful encoders and decoders. Such codec interfaces allow for the efficient processing of data as it is made available while maintaining small actively processing footprints. Of course these aspects depend on the implementation as well however this API standardizes the minimum set of interfaces associated with codec's that are stateful. Until this API is added to the commons-codec project several interfaces and classes here are duplicated to minimize the number of dependencies: namely a dependency on commons-codec will be avoided.
directory-asn1 » asn1-codec

MINA
MINA (Multipurpose Infrastructure for Network Applications) is a network application framework which helps users develop high performance and high scalability network applications easily.
directory-network » mina

excalibur-naming

excalibur-naming » excalibur-naming

ldap-common

directory.directory » ldap-common

ldap-common

ldapd-common » ldap-common

ldapd-common

ldapd-common » ldapd-common

commons-naming-core

commons-naming » commons-naming-core

commons-naming-factory

commons-naming » commons-naming-factory

ldap-snacc-provider

directory-shared » ldap-snacc-provider

ldap-common

directory » ldap-common

jndi

javax.naming » jndi

ldapsdk

ldapsdk » ldapsdk

Naming Config

directory-naming » naming-config

Naming Resources

directory-naming » naming-resources

Naming Core

directory-naming » naming-core

Naming Management

directory-naming » naming-management

Naming Factories

directory-naming » naming-factory

Naming Java

directory-naming » naming-java