Download JAR files tagged by implementations with all dependencies

Tinder is a Java based XMPP library, providing an implementation for XMPP stanzas and components. Tinders origins lie in code that's shared between Jive Software's Openfire and Whack implementations. The implementation that's provided in Tinder hasn't been written again from scratch. Instead, code has been moved from the original projects into Tinder, preserving al of the existing features and functionality. Most of the code that's now in Tinder is based on the org.xmpp package implementation that previously existed in Openfire and Whack. This is the code that defines classes such as Packet, JID, IQ, Component and their extensions. Additionally, some multi-purpose code (such as the DataForm and Result Set Management implementations have been moved to Tinder as well.

The crypto4j library provides a simple and pluggable crypto abstraction library for Java, including both cryptographic primitives and the artifacts defined in the JOSE standard. This library separates the cryptographic primitives from the JOSE artifacts. The library uses the algorithms available through JCA (JCE). The implementations of the cryptographic primitives provided in this library rely on the standard JCA implementation, and can be configured and extended through the JCA mechanisms. The JOSE portion of the library allows custom extensions by either replacing the provided JOSE artifact implementations with custom implementations, or by adding new JOSE artifacts, for instance in form of additional algorithms, which is particularly useful in case that the JOSE standard is updated or in case custom extensions to the JOSE standard should be implemented. The implementations available in this library generally come in two variants: a standard implementation of the primitives and advanced algorithms, and a high-performance implementation that takes advantage of implementation patterns that do not compromise cryprographic security, but speed up the overall processing time.

SEPIA provides implementations for various types of Petri nets. Along Place/Transition-nets, it supports Petri nets with distinguishable token colors and defines coloured workflow nets, where coloured tokens are interpreted as data elements used during process execution. To support information flow analysis of processes, SEPIA defines so-called IF-Nets, tailored for security-oriented workflow modeling which enable users to assign security-levels (HIGH, LOW) to transitions, data elements and persons/agents participating in the process execution.

Skeletal implementation of interface javax.lang.model.util.Types, plus concrete realization backed by core Java Reflection API, akin to JEP 119. This module implements those methods in interface javax.lang.model.util.Types that pertain to the Java type system, plus it provides a method for resolving formal type parameters to actual type arguments. These methods have no equivalent in the Java Reflection API. The abstract skeletal implementation in this module is meant to be specialized for a particular javax.lang.model implementation. The abstraction makes this module well-suited to be used in projects that contain javax.lang.model as part of their domain model (for instance, implementations of alternative languages on top of the JVM).

Rserve is a TCP/IP server which allows other programs to use facilities of R (see www.r-project.org) from various languages without the need to initialize R or link against R library. Every connection has a separate workspace and working directory. Client-side implementations are available for popular languages such as C/C++, PHP and Java. Rserve supports remote connection, authentication and file transfer. Typical use is to integrate R backend for computation of statstical models, plots etc. in other applications.

Asynchronous publish-subscribe communication library. Features: 1. Listeners are stored using WeakReferences to prevent memory leaks when they are not unsubscribed. 2. Uses fork-join framework for concurrent event delivery. 3. Publish methods returns collection of Futures that represent event notifications. 4. Supports ordered publishing: guaranteed to notify of the events in order they were published. 5. Provides EventSource and EventService interfaces for better integration with IOC containers and alternative implementations.

Siena is a persistence abstraction layer made in Java with various implementations: * siena-jdbc: persists objects into a relational database using JDBC (status: deeply tested) * siena-gae: persists objects into the Google App Engine's datastore using its low-level API (status: beta) * siena-sdb: persists objects using Amazon's SimpleDB (very experimental) * siena-remote: persists objects remotely using a remote web application that uses siena. (planning) Siena is also: * Intrusive. You make a class persistent by extending a certain class. Relationships are defined also in an intrusive way. * Simple. Simplicity is the most important thing. * Limited. Due to the simplicity there are several unsupported things such as JOINs. * Extensible. There are two interfaces you can implement on your own way.

BRAP is a Java and Android remoting protocol that uses native Java object serialization, encapsulated in HTTP. It aims to be an alternative to Spring HttpInvoker and Spring Security especially when you don't need or want the dependencies of Spring in your client, for example when building a rich client app or an Android app where size is important. The authentication mechanism lets you use your own domain objects as credentials. Server configuration can be expressed solely in web.xml or by subclassing the ProxyServlet but there is also an optional SpringProxyServlet available for seamless Spring Integration. BRAP focuses on being easy to use, small in size (9 kb), yet powerful and extensible. The client uses a pluggable TransportProvider with default implementations for HttpURLConnection and Apache HttpClient.