Download JAR files tagged by registered with all dependencies

The Sakai Wicket Maven Archetype allows you to generate a sample Sakai app via a single Maven command. The app is based on Apache Wicket which integrates nicely with Sakai. The app demonstrates how to get a Sakai tool styled, internationalised and registered, setup your own APIs, wire them up with Spring and inject them via annotations. The 1.1 and up releases also include multi database support via Spring JDBC. It could easily be used as a base for a real tool.

Model Citizen is an annotation based model factory for Java. A Model is mapped by a Blueprint using annotated fields. Blueprints contain default values and references to other blueprinted models. The ModelFactory can create Models based on registered Blueprints. A Model already created can be passed into the ModelFactory as a Reference Model, which will be used as the basis for the new Model.

There are two ways to use OSGi in server-side[1]. In Carbon, what we have done is, embedding an OSGi framework inside a servlet container. So BridgeServlet delegates all the request from the servlet container to the HttpServiceServlet registered by the http.bridge bundle. This is required only when Carbon is running inside a webapp. There is a possibility to embed an HTTP server(ex. jetty) inside equinox and start a server with all our carbon bundles. This is same as running carbon inside spring DM server. For this scenario, we do not need org.wso2.carbon.http.bridge bundles and the org.wso2.carbon.bridge extension bundle. 1. http://eclipse.org/equinox/server/http_quickstart.php

This plugin provides a registered action, toolbar button and menu actions which can clear the REUSE flag <b>preventing a file from being replaced</b>. <br/><br/> The toolbar button, which looks like a "push pin", provides a visual indication that the currently active editor is REUSEable; the button is only enabled when the active editor is REUSEable. <br/><br/> In some situations the IDE/platform opens a file with the REUSE flag (see NetBeans API doc Line.ShowOpenType); files opened like this can be automatically replaced in an editor window by other files. <br/><br/> IDE REUSE examples: single stepping into a file, clicking on a stacktrace for goto source, jVi tag-stack operations.

A plugin for the Apache Felix Webconsole. When installed, this bundle will add a tab on the Web Console that provides a graphic overview of the OSGi framework, including services, bundles, and components. Colors are used to encode the different states. Bundles are shown to be started, stopped, starting, resolved, and installed. Services are shown to be used, looked for, or registered in the air. Components can be seen to be operating or not satisfied. Most objects have a tooltip with extra information and all objects can be clicked upon. Hovering over a bundle or service shows only the conenections to/from the component. The display updates every 5 seconds to provide a continuous view on the operations of the framework it runs on.

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.

A plugin for the Apache Felix Webconsole. When installed, this bundle will add a tab on the Web Console that provides a graphic overview of the OSGi framework, including services, bundles, and components. Colors are used to encode the different states. Bundles are shown to be started, stopped, starting, resolved, and installed. Services are shown to be used, looked for, or registered in the air. Components can be seen to be operating or not satisfied. Most objects have a tooltip with extra information and all objects can be clicked upon. Hovering over a bundle or service shows only the conenections to/from the component. The display updates every 5 seconds to provide a continuous view on the operations of the framework it runs on.

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.

This plugin provides integration between Spring and Maven. Plugin goals support loading a Spring context XML file as part of the Maven build lifecycle. The XML file can be on the local file system or be accessible via any URL Spring's resource loading mechanism can understand. Spring's "classpath:context.xml" style notation is supported. Annotated Java classes can also be used to load a Spring context. Maven properties are injected into the Spring context (both XML and annotation style) as a java.util.Properties bean named "mavenProperties". Maven properties are also registered as a top level PropertySource so that Spring's placeholder resolution framework automatically considers them. See Project Reports -> Plugin Documentation for details on plugin goals. By default, the profile "maven" is set as an active Spring profile along with any other active Maven profiles.

Rouplex-Niossl is a java SPI (service provider interface) for secure (SSL/TLS), selectable, socket channels. Some of the classes in the java.nio.channels package have been extended by secure counterparts that can be used side by side, or replace existing instances of the plain implementations. This package contains just the entry point calls for instantiating such instances, as well as a non-functional, default implementation. For a concrete implementation of these classes you can take a look at Rouplex-Niossl-Spi, which would be included as a separate dependency to your applications. More specifically this library defines SSLSocketChannel class to inherit from SocketChannel, SSLServerSocketChannel to inherit from ServerSocketChannel and SSLSelector to inherit from SSLSelector. One or more instances of SSLSocketChannel can be registered with an (or more) instance of SSLSelector to be selected upon, with the same exact semantics a SocketChannel would expect from registering with a Selector. Further, a mixture of SocketChannels and SSLSocketChannels can be registered simultaneously with an SSLSelector. The secure counterparts abide to the same API and semantics defined for plain channels at https://docs.oracle.com/javase/8/docs/api/java/nio/channels/package-summary.html. This way, the existing products can be easily updated to provide secure communication and new products can achieve security of data in transit by using the already proven and excellent patterns for communication such as nio.