I have created an app kit for building OSGi applications using Equinox with Bndtools at:
The app kit is split across several branches so that you may choose the content that best suits your application. Each main branch has a corresponding examples branch that contains a working example. You will find launchers in the dev project for the base framework, and in the example projects for running the examples.
- master : bare bones OSGi with a working console
- ds : master + declarative services
- web : ds + servlets
- rest : web + JAX-RS
- mongo-rest : rest + MongoDB
Hopefully this will make it a bit easier to get started with OSGi.
I have released eMongo version 1.1.0. eMongo provides a set of OSGi services for interfacing to MongoDB. This version fixes a minor bug with the metatype description data and adds the ability to persist OSGi log entries to a MongoDB collection. Details can be found on the wiki.
I have released eModeling version 1.0.0. eModeling provides a set of OSGi services and extensions for EMF. Features include:
- Services for creating and configuring an EMF ResourceSet with custom URI handlers
- A service for creating URI mappings from service configuration properties – includes metatype
- A service for creating a ResourceSet that can be used like a cache in the UI thread
- An EMF model of generic collections
- An EMF model for storing OSGi log data
- An EMF model for creating and parsing a simple model query expression
- Custom Hamcrest matchers for comparing two EMF model object instances for equality
For more information, please see the wiki.
This project is the last dependency to be released from a large refactoring of MongoEMF. Now that eModeling is finished, I can complete the MongoEMF 0.8.0 release. I hope to have this completed by the end of the year.
I have released eMongo version 1.0.0. eMongo provides a set of OSGi services for interfacing to MongoDB. The main advantage to using eMongo is in an enterprise environment where you would like to configure your database parameters like hostname, user, password, etc without having to re-deploy your server. eMongo services utilize the OSGi metatype service which, when combined with the Apache Felix Web Console, gives the administrator a convenient UI for configuring the MongoDB driver. Access to a MongoDB database is split between two services: one for the client connection, and one for the database. Here is the configuration through the web console:
Once the client connection is configured, you may configure one or more databases attached to that client:
The developer API is very simple. Here is an example of an OSGi component accessing a MongoDB database:
public class MyComponent
private volatile MongoDatabaseProvider mongoDatabaseProvider;
public void activate()
DB database = mongoDatabaseProvider.getDB();
DBCollection collection = database.getCollection("items");
@Reference(unbind = "-", target = "(alias=primary)")
public void bindMongoDatabaseProvider(MongoDatabaseProvider mongoDatabaseProvider)
this.mongoDatabaseProvider = mongoDatabaseProvider;
There are a few additional features like a service for creating a sequential record ID, and a JUnit rule for unit testing. For more information, please see the eMongo Wiki.
I have released eUnit version 1.0.0. eUnit is a utility framework to assist with JUnit testing in an OSGi environment. The primary feature available in this first version is a JUnit @Rule for locating an OSGi service. Here is a simple example:
public ServiceLocator<LogService> logServiceLocator = new ServiceLocator<LogService>(LogService.class);
private LogService logService;
public void setUp()
logService = logServiceLocator.getService();
This framework is the result of a large refactoring of my MongoEMF framework. I have split that project into smaller, standalone, projects and I will be releasing additional content over the next couple of months.