Funcito is a Java library which simplifies access to your favorite functional programming APIs by wrapping Java methods as the function-type objects defined in those libraries. Rather than creating another functional programming API, Funcito makes it easy to define function-type objects which wrap existing methods. As a result, your code has less noise and clutter of anonymous inner classes, annotations, etc. Your code remains safe for automated refactoring, since there are no String-based reflection or forced naming conventions. The supported frameworks are Google Guava, Jedi, Functional Java, Play! Framework 2, collections-generic, and Netflix RxJava.
CRest (Client REST) is a lightweight library that simplifies the integration of third party RESTful services into Java applications. CRest is mainly annotation-driven, allowing the developer to focus on the essential aspects of the integration of a REST service, such as the definition of the Java interface that maps the remote REST methods and the data model the interface will deal with. The rest is achieved by annotating a plain Java interface with the relevant information such as the service end-point, the desired timeouts, URL formats, etc. CRest will handle everything else, including HTTP request generation, auto marshalling of the response, and more.
Geomajas profiling project is a simple application profiling system that can be used to continuously gather profiling information in a running application. It allows you to get the number of invocations and total/average time. Profiling data can also be grouped to allow total time to be split up over different groups. There is utility code to use this for JDBC access profiling, and JMX integration for accessing the data which is gathered and reset the counters.
The Geomajas API project contains some annotations that can be used to indicate which parts (which classes and which (public) methods or fields) are considered as the API. This is particularly useful for projects where you want to mark the API without the need to refactor everything to interfaces and factories.
Hades is a high availability (HA) data source. This HA data source contains two other data sources: the main one and the failover one. The HA data source exposes one of them at a time and can automatically switch between them when certain conditions are met. These conditions are highly configurable. By default, when the main data source is overloaded, the failover data source is used. The load of a data base is determined on the basis of the average execution time of some configurable SQL statement that is examined periodically. The HA data source exposes through JMX its state and also operations for manual switching between the two contained data sources in case automatic switching must be suppressed for some reason.