Download JAR files tagged by container with all dependencies

Metro is a high-performance, extensible, easy-to-use web service stack. It is a one-stop shop for all your web service needs, from the simplest hello world web service to reliable, secured, and transacted web service that involves .NET services. This is the top module for the Metro project. This is the module you should depend upon by default. The Maven distribution is meant for use of Metro outside a container. For Tomcat or GlassFish please use the regular distribution with its installation scripts.

SpringUnit is a Java unit testing framework that combines Spring's dependency injection container with JUnit's test execution environment. It facilitates the creation of data-driven tests, where the data inputs and expected outcomes are defined in XML files and the test logic resides in Java source code.

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

The Config project is home to Sakai configuration and localization files. Config includes several versions of sakai.properties, a text file containing a series of key/value pairs that provide a convenient mechanism for defining a variety of configuration options for Sakai tools, services, supporting database and UI-related text such as copyright statement, institutional name, server name, etc. Settings in sakai.properties are read on startup; thus changes to sakai.properties only take effect after you restart Sakai's servlet container (typically Apache Tomcat).

This nifi-utils module should be a general purpose place to store widely and generally useful functions that any component might want to leverage. NO DEPENDENCIES should be added. This module is likely to be leveraged by every extension and should not bring along any other dependencies. The only dependency intended is the nifi-api and even this is expected to be already provided in any case where it would be used. The typical place this util would be found is within a nar and all nars already have nifi-api as a parent dependency. The nifi-api can be thought of as a NiFi Application Container level dependency.

This Lutra submodule provides a common framework that other submodules in Lutra use and extend. It includes an implementation of OTTR's data model with classes for templates, instances, types, etc.; a system for handling results and error messages; core interfaces and abstract classes for streamed pipelines for parsing and writing templates and instances; as well as implementation of the TemplateStore, a container for templates, with algorithms for checking correctness of templates and expanding and checking correctness of instances. Lutra is the reference implementation of the OTTR framework. For more information about OTTR, see http://ottr.xyz.