Download JAR files tagged by components with all dependencies

This bundle wraps Pi4j (http://pi4j.com) that wraps the native code Wiring Pi (http://wiringpi.com). It wraps these libraries to make them OSGi friendly and allow them to work together with the OSGi enRoute IoT circuit library (osgi.enroute.iot.circuit). The bundle will first use Pi4J to detect on what hardware it runs. If it runs on an appropriate type, it will register a component that can be configured with Metatype. The Metatype defines a full blown configuration template for all the Pi's functions. The GPIO's are registered as components for the circuit. Regardless of the success of the configuration, this bundle will also register a GpioController service, which is the main Pi4J class.

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 Infinispan Spring Integration project provides Spring integration for Infinispan, a high performance distributed cache. Its primary features are * An implementation of org.springframework.cache.CacheManager, Spring's central caching abstraction, backed by Infinispan's EmbeddedCacheManager. To be used if your Spring-powered application and Infinispan are colocated, i.e. running within the same VM. * An implementation of org.springframework.cache.CacheManager backed by Infinispan's RemoteCacheManager. To bes used if your Spring-powered application accesses Infinispan remotely, i.e. over the network. * An implementation of org.springframework.cache.CacheManager backed by a CacheContainer reference. To be used if your Spring- powered application needs access to a CacheContainer defined outside the application (e.g. retrieved from JNDI) * Spring namespace support allowing shortcut definitions for all the components above In addition, Infinispan Spring Integration offers various FactoryBeans for facilitating creation of Infinispan core classes - Cache, CacheManager, ... - within a Spring context.

GWTUpload is a library for uploading files to web servers, showing a progress bar with real information about the process (file size, bytes transferred, etc). It uses ajax requests to ask the web server for the upload progress. It has two components written in java, the server side with servlet and utility classes, and the client side that is compiled into javascript using gwt. GWTUpload-gae is a library with aditional classes needed for using GwtUpload in Google Application Engine (GAE). JSUpload is the client library but compiled and exported into javascript, so users without Gwt skills can use it directly in their web pages. It includes a bunch of useful examples to learn how to use the library and see its features.

The Jeuron Application Platform is a lightweight framework to assemble software components intended to support multiple project and deployment scenarios while also providing an environment for testing and debugging. The platform is comprised of a set of packages which provide transport, messaging, configuration, and execution services designed to create a configurable, scalable, and distributed application environment. The low resource model permits the platform to be instantiated during each build cycle and to be deployed at all levels of the application hierarchy such as application servers, web servers, and mobile or wired workstations.

MOCCA is the Message-Oriented Command and Context Architecture, providing a GLUE middle-ware that allows sending commands to a peer which are executed by state-less handlers in a specific context. In contrast to the Request-Response scheme the message flow is not fixed by the framework. This allows to implement different communication paradigms (including Request-Response). The whole system can be seen as an automaton with Messages that trigger state transitions in the local Contexts. This library contains the core components, including the GLUE-based implementation.