Download JAR files tagged by bundles with all dependencies

The Eclipse extension registry allows bundles to communicate and cooperate using declarative markup and lazy instantiation. The extension mechanism is similar to OSGi services and declarative services but has some different contractual and management characteristics.

While most bundles work quite find with the typical wrapped bundle code from poms/wrapped there are some special cases where it does not work this way. This parent contains all bundles which are not meant to be wrapped in the classical way, but require some additional, special work.

A bundle project producing JAX-RS RI bundles. The primary artifact is an "all-in-one" OSGi-fied JAX-RS RI bundle (jaxrs-ri.jar). Attached to that are two compressed JAX-RS RI archives. The first archive (jaxrs-ri.zip) consists of binary RI bits and contains the API jar (under "api" directory), RI libraries (under "lib" directory) as well as all external RI dependencies (under "ext" directory). The secondary archive (jaxrs-ri-src.zip) contains buildable JAX-RS RI source bundle and contains the API jar (under "api" directory), RI sources (under "src" directory) as well as all external RI dependencies (under "ext" directory). The second archive also contains "build.xml" ANT script that builds the RI sources. To build the JAX-RS RI simply unzip the archive, cd to the created jaxrs-ri directory and invoke "ant" from the command line.

A main program (executable JAR) that will listen to port 29998. At first, it can only answer that it is an Envoy (a limited agent). The only function it supports is installing a -runpath. It will then create a framework + agent and transfer the connection to the just installed agent who will then install the bundles. This JAR is a main command for JPM called bndremote. In JPM, it will start up with debug enabled. This JAR does some highly complicated class loading wizardy to ensure that it does not enforce any constraints on the -runpath.

A main program (executable JAR) that will listen to port 29998. At first, it can only answer that it is an Envoy (a limited agent). The only function it supports is installing a -runpath. It will then create a framework + agent and transfer the connection to the just installed agent who will then install the bundles. This JAR is a main command for JPM called bndremote. In JPM, it will start up with debug enabled. This JAR does some highly complicated class loading wizardy to ensure that it does not enforce any constraints on the -runpath.

This bundle acts as an agent for the remote launching architecture. When started, it will bind to port 29998 and listens for incoming requests. When this port is accessed, it will open a link that allows it to act as an OSGi management agent that is remotely controlled. When this connection is closed, it will remove all bundles that were installed through this connection. The protocol is highly optimized to make this also work for small devices and slow connections.

Tracer provides support for enabling the logs for specific category at specific level and only for specific request. It provides a very fine level of control via config provided as part of HTTP request around how the logging should be performed for given category. Refer to http://sling.apache.org/documentation/bundles/log-tracers.html

Bundles required by the Apache Marmotta Kiwi Repository. This list includes DB drivers for H2 and Postgres and caching dependencies for Guava and Hazelcast. Dependencies for other supported options (MySQL, Infinispan, EH Cache) are commented. Users that want to use such options will need to create their own version of this bundle list or to provide the commented bundles by some other means.

Interfaces to be implemented by Domains, Connectors and Events which handle intatiation of Services and Proxies, classes for registration of bundles and services, classes for localization, classes that save connector properties (Persistence) and finally classes that enable the web application to have access to OSGI bundles. This bundle contains only the model and interface descriptions of all those services. In theory someone can take only a minor number of openengsb bundles, the api and create the rest of the system on his own.

OSGi bundle that contains the JDBC API coming from OpenJDK 1.7. In case of OSGi, it is better to exclude javax.sql.*, com.sun.rowset.* and javax.transaction.* packages from the boot classpath and use them from bundles. Very often javax.transaction.* packages are used from a custom bundle. As javax.sql.XADataSource wires to that package, it is logical to have that in a custom bundle as well so there will be no package wiring issues.