Knapsack is a custom launcher for the Apache Felix OSGi Framework with native shell integration and a few default services that run out of the box. See http://kgilmer.github.com/knapsack/ for more information about its design.
Jitsi (previously SIP Communicator) is an audio/video and chat communicator that supports protocols such as SIP, XMPP/Jabber, AIM/ICQ, Windows Live, Yahoo!, Bonjour and many other useful features. Jitsi is Open Source / Free Software, and is available under the terms of the LGPL.
The application is developed (mostly) in Java and basd on OSGi.
http://www.jitsi.org/
Clerezza is a service platform based on OSGi (Open Services Gateway initiative) which provides a set of functionality for management of semantically linked data accessable through RESTful Web Services and in a secured way. Furthermore, Clerezza allows to easily develop semantic web applications by providing tools to manipulate RDF data, create RESTful Web Services and Renderlets using ScalaServerPages.
Contents are stored as triples based on W3C RDF specification. These triples are stored via Clerezza's Smart Content Binding (SCB). SCB defines a technology-agnostic layer to access and modify triple stores. It provides a java implementation of the graph data model specified by W3C RDF and functionalities to operate on that data model. SCB offers a service interface to access multiple named graphs and it can use various weighted providers to manage RDF graphs in a technology specific manner, e.g., using Jena or Sesame. It also provides for adaptors that allow an application to use various APIs (including the Jena api) to process RDF graphs. Furthermore, SCB offers a serialization and a parsing service to convert a graph into a certain representation (format) and vice versa. http://incubator.apache.org/clerezza/
PojoSR is a service registry that enables OSGi style service registry programs without using an OSGi framework.
The idea is to create something that would make the service and parts of the life cycle layer of OSGi available in environments where it typically isn't.
PojoSR can also be run on Google App Engine
How to run Apache Felix OSGI framework on Android.
https://cwiki.apache.org/confluence/display/FELIX/Apache+Felix+Framework+and+...
The open Home Automation Bus (openHAB) project aims at providing a universal integration platform for all things around home automation.
It is designed to be absolutely vendor-neutral as well as hardware/protocol-agnostic. openHAB brings together different bus systems, hardware devices and interface protocols by dedicated bindings. These bindings send and receive commands and status updates on the openHAB event bus. This concept allows designing user interfaces with a unique look&feel, but with the possibility to operate devices based on a big number of different technologies. Besides the user interfaces, it also brings the power of automation logics across different system boundaries.
openHAB is a pure Java solution, fully based on OSGi. The Equinox OSGi runtime and Jetty as a web server build the core foundation of the runtime.
The openHAB Designer, which is the configuration tool for the openHAB Runtime, is an Eclipse RCP application with Xtext-based editors to offer a highly user-friendly way of editing configuration files, UI definitions and automation rules. For the automation rules, JBoss Drools builds the backbone.
If you are a fan of Java/OSGi/Eclipse, openHAB should be the perfect match for you. If you are not, you might want to consider other tools like Misterhouse, which aim at almost the same thing and are very mature already.
As the OSGi platform allows a highly modular architecture, the bindings are realized as different bundles, which can be dynamically plugged to openHAB, so that every user can decide on the bindings he is interested in.
Here are some examples for bindings (but please be aware that most are not yet implemented):
Currently, there is only one user interface available for openHAB, a web-based UI, which can be used from many different devices. Nonetheless, openHAB is designed in a way that there can easily be added further user interfaces; be it a remote terminal or a native iPad application.
http://code.google.com/p/openhab/
OSGi services can be easily configured using the ConfigurationAdmin service. If you add metadata to your services, they can be configured with a nice user interface such as the Apache Web Console. This tutorial will walk you through the steps to create the metadata, set up the web console, and configure your services.
The OSGi specification (R4.2) introduced a provisional specification called composite bundles. In this talk the lead developers of two prominent open source OSGi framework implementations will join forces to discuss lessons learned with the provisional composite bundle specification and what improvements are expected for the next release of the core framework specification for composite bundles. Richard Hall is the chair of the Apache Felix project and Tom Watson is the co-lead of the Eclipse Equinox project. Together they will explain the issues with the R4.2 provisional composite specification and discuss the changes being done in order to graduate the composite bundle specification for the next OSGi core specification release.
The OSGi framework provides a powerful runtime for the Java platform, which promotes strong modularity, versioning and dynamic management of applications. Bundles (or modules) installed in the framework are expected to collaborate and live together sharing the same service registry and public class space. Until now there was no standard way to provide additional isolation to a group of bundles installed in a single framework. In this talk we will discuss how composite bundles can be used to provide additional isolation to a group of bundles or applications installed into the framework. Composite bundles are managed in a similar way as other bundles installed into an OSGi framework. The key difference is the content of a composite bundle is composed by a set of bundles called constituents. Conceptually a composite bundle provides a virtual framework, called a composite framework, where constituent bundles are installed and running. The composite bundle can be used to manage the composite framework. Composite bundles support a two-way relationship between the parent framework and composite framework instances, where packages and services can be shared from the parent to the composite framework and vice versa. During this talk we will go into the gory details of the composite bundle specification and demonstrate composite bundles running on an OSGi framework implementation.
Poor Man's Provisioning Platform
================================
