Download JAR files tagged by implementations with all dependencies

Dominate is the basement on which all other JavATE libraries are build. It contains interfaces for the basic patterns of domain driven design like "entity" and "repository". These interfaces gives you the possibility to access these objects in a standardized way allowing a lot of generalization and simplification. Side by side with these interfaces there are implementations that speed up the development of application using mainstream technologies like Hibernate, JPA, JCR and MongoDB.

The Proton system tests execute against either the Java or the C implementations, based on the chosen profile. To execute, run either "mvn test -P proton-j" or "mvn test -P proton-jni". To reduce the set of Python tests run, set system property proton.pythontest.pattern, for example: mvn test -Dproton.pythontest.pattern='proton_tests.transport.TransportTest.*' The proton-jni profile looks for the JNI jar and native libraries under directory <basedir>/build/proton-c. To override this, run Maven like so: "mvn test -P proton-jni -Dproton-c-build-dir=/path/to/build/dir".

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.

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.

The Java Data Objects 2.0 (JDO) API is a standard interface-based Java model abstraction of persistence, developed as Java Specification Request JSR 243 under the auspices of the Java Community Process. The JDO TCK is a test suite designed to test implementations of the Java Data Objects specification. In order to claim compatibility with JDO, an implementation must pass all relevant tests of the JDOTCK. NOTE!! There are no unit tests in this project.

Brownies Collections complements the Java Collections Framework. GapList combines the strengths of both ArrayList and LinkedList. BigList is a list optimized for storing large number of elements. There are specialized List implementations for all primitive data types (IntGapList, IntBigList, IntObjGapList, IntObjBigList). The key collection classes offer support for keys and constraints for lists and collections (KeyList, KeyCollection, KeySet, Key1List, Key1Collection, Key1Set, Key2List, Key2Collection, Key2Set).

Dryuf BigIo is stateless, unlimited IO framework, solving few design problems of original JDK. It mainly provides three things - FlatBuffer with 64-bit address space and being stateless. Additionally, it provides FlatChannel interface and few implementations - providing the arbitrary reads and writes from chosen position. This is implemented only in FileChannel in NIO so this interface makes it easier to provide those stateless reads and writes on virtual channels too. BigIo also provides committable objects, allowing marking the object as completed or incomplete, so it correctly results into success or exception on receiving side.

ZooKeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these kinds of services are used in some form or another by distributed applications. Each time they are implemented there is a lot of work that goes into fixing the bugs and race conditions that are inevitable. Because of the difficulty of implementing these kinds of services, applications initially usually skimp on them ,which make them brittle in the presence of change and difficult to manage. Even when done correctly, different implementations of these services lead to management complexity when the applications are deployed.