Download JAR files tagged by query with all dependencies

Apache Empire-db is an Open Source relational data persistence component which allows database vendor independent dynamic query definition as well as safe and simple data retrieval and updating. Compared to most other solutions like e.g. Hibernate, TopLink, iBATIS or JPA implementations, Empire-db takes a considerably different approach, with a special focus on compile-time safety, reduced redundancies and improved developer productivity.

The bit array data structure is implemented in Java as the BitSet class. Unfortunately, this fails to scale without compression. JavaEWAH is a word-aligned compressed variant of the Java bitset class. It uses a 64-bit run-length encoding (RLE) compression scheme. The goal of word-aligned compression is not to achieve the best compression, but rather to improve query processing time. Hence, we try to save CPU cycles, maybe at the expense of storage. However, the EWAH scheme we implemented is always more efficient storage-wise than an uncompressed bitmap (implemented in Java as the BitSet class). Unlike some alternatives, javaewah does not rely on a patented scheme.

JPA Security is an Access Control Solution for the Java Persistence API (JPA). With JPA Security your access control can be performed in the database. You may query the database for all objects of a certain type and will receive only the objects you have read access for. This filtering is performed in the database. Unaccessible queried objects will not be loaded into memory. JPA Security enables you to completely remove security-related code from your code-base. All access control may be configured via Annotations or XML. With JPA Security you do not have to change your access control paradigm (but maybe you want to, when you see the great capability of JPA Security). You even can mix access control paradigms easily. JPA Security is not designed to replace current security solutions, but to extend them. It integrates smoothly into the security mechanisms of the Java EE Platform, but may be used with third-party frameworks like Spring Security or in Java SE, too. With the extensibility of JPA Security it is easy to provide your own access control paradigm, access rules storage or login mechanism.

A scalable, concurrent, in-memory Key Value (KV) map. Oak implements a concurrent Key-Value map that can keep all keys and values off-heap. This enables working with bigger heap sizes than JVM's managed heap. OakMap implements an API similar to the industry standard Java8 ConcurrentNavigableMap API. It provides strong (atomic) semantics for read, write, and read-modify-write, as well as (non-atomic) range query (scan) operations, both forward and backward. OakMap is optimized for big keys and values, in particular, for incremental maintenance of objects (update in-place). It is faster and scales better with additional CPU cores than the popular Java ConcurrentNavigableMap ConcurrentSkipListMap