Maven Repository: jndi

1. directory-shared » Apache's ASN.1 based LDAP BER Message Provider

   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.

2. directory-shared » Common LDAP API
   
   
   

   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.

3. directory-shared » Kerberos Common

   Kerberos Common - Common Kerberos 5 classes.

4. directory-shared » Apache's new ASN.1 based LDAP BER Message Provider
   
   
   

   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.

5. directory-network » MINA

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

6. net.sf.ldaptemplate » LdapTemplate

   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.

7. directory-clients » ldap-clients

   ldap-clients - Java LDAP Clients

8. directory-asn1 » ASN.1 DER Runtime

   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.

9. directory-asn1 » Apache ASN.1

   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.

10. directory-asn1 » Stateful chunking codec API for ASN.1 runtime

    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.

11. directory-asn1 » ASN.1 new BER Runtime

    ASN.1 new BER Runtime - A new BER implementation

12. directory-asn1 » ASN.1 BER Runtime

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

13. directory-asn1 » ASN1 Stub Compiler

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

14. simple-jndi » simple-jndi

    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.

15. directory-protocols » Kerberos Protocol Provider

    Kerberos Protocol Provider - A protocol provider for Kerberos handlers and codecs.

16. directory-protocols » ApacheDS LDAP Provider

    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.

17. directory.directory » ApacheDS Shared

    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.

18. directory.directory » Apache Directory Project

    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.

19. directory.directory » ApacheDS Main

    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.

20. directory.directory » ApacheDS Core

    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.

21. directory » ApacheDS Main

    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.

22. directory » ApacheDS Shared

    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.

23. directory » ApacheDS Core

    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.

24. directory » ApacheDS Plugin

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

25. directory » Apache Directory Project

    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.

26. excalibur-naming » excalibur-naming

    excalibur-naming -

27. directory-naming » Naming Resources

    Naming Resources -

28. directory-naming » Naming Core

    Naming Core -

29. directory-naming » Naming Config

    Naming Config -

30. directory-naming » Naming Factories

    Naming Factories -

31. directory-naming » Naming Java

    Naming Java -

32. directory-naming » Naming Management

    Naming Management -

33. directory-shared » ldap-snacc-provider

    ldap-snacc-provider -

34. javax.naming » jndi

    jndi -

35. ldapsdk » ldapsdk

    ldapsdk -

36. ldapd-common » ldap-common

    ldap-common -

37. ldapd-common » ldapd-common

    ldapd-common -

38. directory.directory » ldap-common

    ldap-common -

39. directory » ldap-common

    ldap-common -

40. commons-naming » commons-naming-core

    commons-naming-core -

41. commons-naming » commons-naming-factory

    commons-naming-factory -