Skip to site navigation (Press enter)

[CONF] Apache Felix > Apache Felix Application Demonstration

confluence Wed, 30 May 2012 11:52:31 -0700

     Apache Felix Application Demonstration
    Page edited by             Benedikt Ritter
    
        
        Comment:
        Rewrite of major parts of the example

    
        

                         Changes (52)
                                 
    

                    
    
            ...

            In order to follow this example you need three things: 
 

            # a [Subversion|http://subversion.apache.org/] client to check out the source code
# the IDE of your choice to view the source code 

            # [Maven|http://maven.apache.org] to build the source code 
 

            ...

            !example-application.png|align=center! 
 

            h2. Service-Based Application on top of the Framework 

            h2. Getting the source code 

             

            Currently, the service-based example application is only available in our SVN repository. There are four separate projects that comprise the application, which can be found here: 

            Currently, the example application is only available in our source control repositories. We have created two applications, one for the service and one for the extender-based approach. Both examples can be run as a bundled application on top of any OSGi implementation or by hosting an embedded framework. Assuming you are using svn to get the source code, you can find the source at the following locations: 

             
{noformat} 

            ...

            http://svn.apache.org/repos/asf/felix/trunk/examples/servicebased.square 
http://svn.apache.org/repos/asf/felix/trunk/examples/servicebased.triangle 

             
http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.host 
http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.circle 
http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.square 
http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.triangle 

            {noformat} 
 

            ...

            {noformat} 
 

            Once you have the projects checked out you can go into each sub-directory and build it using Maven; this assumes you have Maven properly installed. To build, simply perform the following in each project directory: 

            h2. Building and running the examples 

             

            Once you have checked out the projects you can go into each sub-directory and build it using Maven; this assumes you have Maven properly installed. To build, simply perform the following in each project directory: 
 

            {noformat} 
mvn clean install 
{noformat} 
 

            Once After you have built the projects, start Felix and then install/start the resulting bundle for one example (service or extender-based) from the {{target/}} directory of each project directory. 

             

            Examine the source code to understand the details of the approach. In the future this documentation will hopefully be expanded to described more details. 

            To start the examples using an embedded framework, export the jars you just build to a folder in your file system. 
Then start the host.jar and pass the names of all services/extensions to the application as parameters: 

             

            h2. Service-Based Application embedding the Framework 

            {noformat} 
java -jar servicebased.host-1.0.0.jar file:/servicebased.circle-1.0.0.jar file:/servicebased.square-1.0.0.jar file:/servicebased.triangle-1.0.0.jar 
{noformat} 

             

            The host bundle from the previous section also implements the hosted framework service-based approach. The host bundle activator has a static {{main()}} method that creates an instance of Felix and loads the shape service bundles. The shape service implementations are the same for both the bundled and hosted framework application versions in this case. To execute the hosted framework application, issue the following command: 

            If you are using an IDE like eclipse, you can run an embedded framework using a custom run configuration. In eclipse click _Run_ -> _Run Configurations..._ and create a new _Java Application_ run configuration. Select the host project you want to start (servicebased.host or extenderbased.host) and chose the {{Application}} class as _Main class_ from the org.apache.felix.example.servicebased/extenderbase.host.launch package. Switch to the _Arguments_ tab and fill in the following _Program arguments_ (assuming you want to run the extenderbased example): 

             
{noformat} 

            java -jar target/servicebased.host-1.0.0.jar 

            file:../extenderbased.circle/target/extenderbased.circle-1.0.0.jar file:../extenderbased.square/target/extenderbased.square-1.0.0.jar file:../extenderbased.triangle/target/extenderbased.triangle-1.0.0.jar 

            {noformat} 
 

            To successfully execute the hosted framework version of the application, you must be in the "servicebased.host" project directory when issuing the above command and you must have already built all of the other projects (i.e., circle, square, triangle). 

            For more details on running an application with an embedded framework scroll down to the bottom of the page. 

             

            Examine the source code to understand the details of the approach. In the future this documentation will hopefully be expanded to described more details. 

            h2. Service-Based Application 

             

            h2. Extender-Based Application on top of the Framework 

            The service-based application uses the OSGi service concept and the service registry as the extensibility mechanism. Therefore the host bundle contains a service interface located at {{org.apache.felix.example.servicebased.host.service.SimpleShape}}. The SimpleShape service has two properties: a name and an icon. Beside that it defines one operation: {{draw(Graphics2D g2, Point p)}}. 

             

            Currently, the extender-based example application is only available in our SVN repository. There are four separate projects that comprise the application, which can be found here: 

            h3. Defining shapes as services 

             

            Bundles that want to contribute a shape service have to implement the {{SimpleShape}} interface. Take a look at the circle bundle for example. The circle bundle only contains one class, the {{Activator}}. A {{[BundleActivator|http://www.osgi.org/javadoc/r4v43/org/osgi/framework/BundleActivator.html]}} is responsible for starting up a bundle. Therefore it gets passed in a {{[BundleContext|http://www.osgi.org/javadoc/r4v43/org/osgi/framework/BundleContext.html]}}, that can be used to perform registration of services within the framework. The {{Activator}} also contains a inner class that implements the {{SimpleShape}} interface and therefore represents the {{SimpleShape}} implementation of a circle. The {{start(BundleContext context}} method is used to register the circle implementation as a service: 
 

            {noformat} 

            http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.host 
http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.circle 
http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.square 
http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.triangle 

            Dictionary<String, Object> dict = new Hashtable<String, Object>(); 
dict.put(SimpleShape.NAME_PROPERTY, "Circle"); 
dict.put(SimpleShape.ICON_PROPERTY, new ImageIcon(this.getClass().getResource("circle.png"))); 
m_context.registerService(SimpleShape.class.getName(), new Circle(), dict); 

            {noformat} 
 

            Check out each project using an appropriate SVN command, such as: 

            First a {{[Dictionary|http://docs.oracle.com/javase/6/docs/api/java/util/Dictionary.html]}} is created to hold the service's properties. The two service properties are added to the dictionary. The icon of the circle service is located under src/main/resources/org/apache/example/servicebased/circle/circle.png. It gets loaded as an {{[ImageIcon|http://docs.oracle.com/javase/6/docs/api/javax/swing/ImageIcon.html]}} and added as icon property. The service then gets registered in the service registry by passing the name of the serivce interface, a service object and the service's properties. 

             

            {noformat} 
svn co http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.host 
{noformat} 

            h3. Detecting shape services 

             

            Once you have the projects checked out you can go into each sub-directory and build it using Maven; this assumes you have Maven properly installed. To build, simply perform the following in each project directory: 

            The host's {{Activator}} creates a {{DrawingFrame}} for displaying the different shapes. It then delegates adding and removing of {{SimpleShape}} services to a {{[ServiceTracker|http://www.osgi.org/javadoc/r4v43/org/osgi/util/tracker/ServiceTracker.html]}} implementation. Then {{ShapeTracker}} gets notified, when a new {{SimpleShape}} service is added to, modified or removed from the service registry. 

             

            h2. Extender-Based Application 
 
In contrast to the service-based example, the extender-based example uses bundles as it's primary extensibility mechanism. Therefore the host bundle containts a {{SimpleShape}} interface, that is much like the one from the service based example. It also containts a {{draw(Graphics2D g2, Point p)}} method and defines a set of properties. This time the properties are not used as properties for registering a service, but for defining bundle header properties, that can be read out from a bundles MANIFEST. 
 
h3. Defining shapes as extensions 
 
Bundles that want to contribute a {{SimpleShape}} extension have to implement the {{SimpleShape}} interface. Have a look at the extender based circle implementation for example. It only contains one class, {{Circle}}, that implements {{SimpleShape}}. Note, that in contrast to the service-based example there is no need to define a {{[BundleActivator|http://www.osgi.org/javadoc/r4v43/org/osgi/framework/BundleActivator.html]}}. This is because, there is no need to register a service within the framework. Information about the provided shape implementation is located in the bundle headers instead. Have a look at the circle's MANIFEST file: 
 

            {noformat} 

            mvn clean install 

            Manifest-Version: 1.0 
Private-Package: org.apache.felix.example.extenderbased.circle 
Tool: Bnd-0.0.238 
Bundle-Name: Apache Felix Circle Extension 
Created-By: Apache Maven Bundle Plugin 
Bundle-Vendor: The Apache Software Foundation 
Build-Jdk: 1.7.0_01 
Bundle-Version: 1.0.0 
Extension-Class: org.apache.felix.example.extenderbased.circle.Circle 
Bnd-LastModified: 1331062969798 
Extension-Icon: org/apache/felix/example/extenderbased/circle/circle.p 
 ng 
Bundle-ManifestVersion: 2 
Bundle-Description: A simple extension for drawing circles. 
Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt 
Bundle-DocURL: http://www.apache.org/ 
Bundle-SymbolicName: org.apache.felix.example.extenderbased.circle 
Import-Package: org.apache.felix.example.extenderbased.host.extension 
Extension-Name: Circle 

            {noformat} 
 

            Once you have built the projects, start Felix and then install/start the resulting bundle from the {{target/}} directory of each project directory. 

            As you can see, the three bundle properties, defined in the {{SimpleShape}} interface are set as bundle headers. 

             

            Examine the source code to understand the details of the approach. In the future this documentation will hopefully be expanded to described more details. 

            Note: The MANIFEST is generated by the maven build, so you will only find it in the compiled jar. If you are intrested in automaticly creating MANIFEST files for your bundles, have a look at the configuration of the [org.apache.felix.maven-bundle-plugin|http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html] in the pom.xml. 

             

            h2. Extender-Based Application embedding the Framework 

            h3. Detecting shape bundles 

             

            The host bundle from the previous section also implements the hosted framework extender-based approach. The host bundle activator has a static {{main()}} method that creates an instance of Felix and loads the shape extension bundles. The shape extension implementations are the same for both bundled and hosted framework application versions in this case. To execute the hosted framework application, issue the following command: 

            Like the {{[ServiceTracker|http://www.osgi.org/javadoc/r4v43/org/osgi/util/tracker/ServiceTracker.html]}} for tracking services, there is a {{[BundleTracker|http://www.osgi.org/javadoc/r4v42/org/osgi/util/tracker/BundleTracker.html]}} for tracking bundles. A {{BundleTracker}} get's notified, when the state of bundles it wants to track change. Have a look at {{org.apache.felix.example.extenderbased.host.ShapeBundleTracker}}. The constructor defines, that only active bundles should be tracked. The {{addingBundle(Bundle bundle, BundleEvent event)}} method gets called by the framework, when a bundle enters the state activated. The tracker then checks, if the bundle headers contain the name property and if so, add the icon to the application. 

             

            {noformat} 
java -jar target/extenderbased.host-1.0.0.jar 
{noformat} 

            h2. Embedding the Framework 

             

            To successfully execute the hosted framework version of the application, you must be in the "extenderbased.host" project directory when issuing the above command and you must have already built all of the other projects (i.e., circle, square, triangle). 

            Since the R4 release the OSGi Framework provides facilities that allow an application to host it's own embedded framework instance. Therefore an implementation of the {{[FrameworkFactory|http://www.osgi.org/javadoc/r4v42/org/osgi/framework/launch/FrameworkFactory.html]}} interface has to be used. OSGi implementors specify their {{FrameworkFactory}} implementation in the {{META-INF/services/org.osgi.framework.launch.FrameworkFactory}} file. Prior to Java 6, one had to parse the class name in that file by oneself. Luckily Java 6 has the {{[ServiceLoader<S>|http://docs.oracle.com/javase/6/docs/api/java/util/ServiceLoader.html]}} class, that lets you easily instantiate a {{FrameworkFactoy}}. Have a look at the contents of the {{org.apache.felix.example.extenderbased.host.launch}} package in the extender-based host bundle (the implementation is the same for the service-based example). 

             

            Examine the source code to understand the details of the approach. In the future this documentation will hopefully be expanded to described more details. 

            The {{Application}} class is responsible for creating the framework and installing and starting the bundles. It uses a {{ConfigUtil}} for creating the framework configuration that is needed to create a framework using the {{FrameworkFactory}}. The {{ConfigUtil}} also creates a temporary cache directory for the framework. If the creation of the framework is successful, {{installAndStartBundles(String... bundleLocations)}} will be called to start the actual application. Therefor the {{Activator}} of the host bundle is instantiated. Note, that the host bundle can not register itself withing the framework it just created. Only the extension bundles will be registered within the framework. 

             

            As you can see no felix specific code is involved in any of the examples. That's one of the advantages of OSGi. Bundles that run on Felix will run on every other implementation of the same OSGi release. 
 

            h2. Feedback 
 

            ...

    
            
    
                            Full Content
                    
        Apache Felix Application Demonstration

(This document is a work in progress.)

Apache Felix provides a foundation for creating modular and dynamically extensible applications. This page presents an example application to demonstrate the various approaches to consider when creating a OSGi/Felix-based application.

It is recommended that you have a look at the more basic examples such as Apache Felix Framework Usage Documentation before you start with this one.

In order to follow this example you need three things:


	a Subversion client to check out the source code
	the IDE of your choice to view the source code
	Maven to build the source code



The source code of the examples is available in the Felix SVN repository at http://svn.apache.org/repos/asf/felix/trunk/examples. If you feel more familiar with git, you can use the git mirror at: git://git.apache.org/felix.git or browse the source code at github: https://github.com/apache/felix

Potential Approaches

When creating an OSGi-based application there are two main orthogonal issues to consider:


	Service model vs. extender model
	Bundled application vs. hosted framework



The first issue is actually a general issue when creating OSGi-based applications. There are two general approaches that can be used when creating an extensible OSGi application. The service model approach uses the OSGi service concept and the service registry as the extensibility mechanism. The extender model approach uses the OSGi installed bundle set as the extensibility mechanism. Both approaches have their advantages and disadvantages and they can be used independently or together.

The second issue is related to whether your application is run completely on top of the OSGi framework as a set of bundles or whether your application hosts an embedded OSGi framework instance. Creating applications completely as a set of bundles is the preferred approach since it allows the application to run on any OSGi framework, but this it not always possible. In such cases where it is not possible or desired, then you may host a framework instance inside your application, which will likely tie your application to that framework implementation.

The remainder of this document will present variations of an example application that demonstrates these different approaches.

Example Application Overview

The example application is a very simple paint program that effectively functions identically whether using services/extensions or running embedded/hosted. The application, called the host, defines a SimpleShape service/extension that it uses to draw shapes. Different implementations of the SimpleShape can be created to allow the application to draw different shapes. Each shape service/extension has name and icon properties that the application uses for manipulating the services/extensions. Available shapes are displayed in the application's tool bar. To draw a shape, click on its button in the tool bar and then click in the drawing canvas. Shapes can be dragged, but not resized. When new shape services/extensions appear they are automatically added to the tool bar and they are automatically removed when the shape services/extensions disappear. Closing the application window causes the framework and the JVM to shut down. The following is a screen shot of the application.



Getting the source code

Currently, the example application is only available in our source control repositories. We have created two applications, one for the service and one for the extender-based approach. Both examples can be run as a bundled application on top of any OSGi implementation or by hosting an embedded framework. Assuming you are using svn to get the source code, you can find the source at the following locations:


http://svn.apache.org/repos/asf/felix/trunk/examples/servicebased.host
http://svn.apache.org/repos/asf/felix/trunk/examples/servicebased.circle
http://svn.apache.org/repos/asf/felix/trunk/examples/servicebased.square
http://svn.apache.org/repos/asf/felix/trunk/examples/servicebased.triangle

http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.host
http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.circle
http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.square
http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.triangle



Check out each project using an appropriate SVN command, such as:


svn co http://svn.apache.org/repos/asf/felix/trunk/examples/servicebased.host



Building and running the examples

Once you have checked out the projects you can go into each sub-directory and build it using Maven; this assumes you have Maven properly installed. To build, simply perform the following in each project directory:


mvn clean install



After you have built the projects, start Felix and then install/start the resulting bundle for one example (service or extender-based) from the target/ directory of each project directory.

To start the examples using an embedded framework, export the jars you just build to a folder in your file system.

Then start the host.jar and pass the names of all services/extensions to the application as parameters:


java -jar servicebased.host-1.0.0.jar file:/servicebased.circle-1.0.0.jar file:/servicebased.square-1.0.0.jar file:/servicebased.triangle-1.0.0.jar



If you are using an IDE like eclipse, you can run an embedded framework using a custom run configuration. In eclipse click Run -> Run Configurations... and create a new Java Application run configuration. Select the host project you want to start (servicebased.host or extenderbased.host) and chose the Application class as Main class from the org.apache.felix.example.servicebased/extenderbase.host.launch package. Switch to the Arguments tab and fill in the following Program arguments (assuming you want to run the extenderbased example):


file:../extenderbased.circle/target/extenderbased.circle-1.0.0.jar file:../extenderbased.square/target/extenderbased.square-1.0.0.jar file:../extenderbased.triangle/target/extenderbased.triangle-1.0.0.jar



For more details on running an application with an embedded framework scroll down to the bottom of the page.

Service-Based Application

The service-based application uses the OSGi service concept and the service registry as the extensibility mechanism. Therefore the host bundle contains a service interface located at org.apache.felix.example.servicebased.host.service.SimpleShape. The SimpleShape service has two properties: a name and an icon. Beside that it defines one operation: draw(Graphics2D g2, Point p).

Defining shapes as services

Bundles that want to contribute a shape service have to implement the SimpleShape interface. Take a look at the circle bundle for example. The circle bundle only contains one class, the Activator. A BundleActivator is responsible for starting up a bundle. Therefore it gets passed in a BundleContext, that can be used to perform registration of services within the framework. The Activator also contains a inner class that implements the SimpleShape interface and therefore represents the SimpleShape implementation of a circle. The start(BundleContext context method is used to register the circle implementation as a service:


Dictionary<String, Object> dict = new Hashtable<String, Object>();
dict.put(SimpleShape.NAME_PROPERTY, "Circle");
dict.put(SimpleShape.ICON_PROPERTY, new ImageIcon(this.getClass().getResource("circle.png")));
m_context.registerService(SimpleShape.class.getName(), new Circle(), dict);



First a Dictionary is created to hold the service's properties. The two service properties are added to the dictionary. The icon of the circle service is located under src/main/resources/org/apache/example/servicebased/circle/circle.png. It gets loaded as an ImageIcon and added as icon property. The service then gets registered in the service registry by passing the name of the serivce interface, a service object and the service's properties.

Detecting shape services

The host's Activator creates a DrawingFrame for displaying the different shapes. It then delegates adding and removing of SimpleShape services to a ServiceTracker implementation. Then ShapeTracker gets notified, when a new SimpleShape service is added to, modified or removed from the service registry.

Extender-Based Application

In contrast to the service-based example, the extender-based example uses bundles as it's primary extensibility mechanism. Therefore the host bundle containts a SimpleShape interface, that is much like the one from the service based example. It also containts a draw(Graphics2D g2, Point p) method and defines a set of properties. This time the properties are not used as properties for registering a service, but for defining bundle header properties, that can be read out from a bundles MANIFEST.

Defining shapes as extensions

Bundles that want to contribute a SimpleShape extension have to implement the SimpleShape interface. Have a look at the extender based circle implementation for example. It only contains one class, Circle, that implements SimpleShape. Note, that in contrast to the service-based example there is no need to define a BundleActivator. This is because, there is no need to register a service within the framework. Information about the provided shape implementation is located in the bundle headers instead. Have a look at the circle's MANIFEST file:


Manifest-Version: 1.0
Private-Package: org.apache.felix.example.extenderbased.circle
Tool: Bnd-0.0.238
Bundle-Name: Apache Felix Circle Extension
Created-By: Apache Maven Bundle Plugin
Bundle-Vendor: The Apache Software Foundation
Build-Jdk: 1.7.0_01
Bundle-Version: 1.0.0
Extension-Class: org.apache.felix.example.extenderbased.circle.Circle
Bnd-LastModified: 1331062969798
Extension-Icon: org/apache/felix/example/extenderbased/circle/circle.p
 ng
Bundle-ManifestVersion: 2
Bundle-Description: A simple extension for drawing circles.
Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt
Bundle-DocURL: http://www.apache.org/
Bundle-SymbolicName: org.apache.felix.example.extenderbased.circle
Import-Package: org.apache.felix.example.extenderbased.host.extension
Extension-Name: Circle



As you can see, the three bundle properties, defined in the SimpleShape interface are set as bundle headers.

Note: The MANIFEST is generated by the maven build, so you will only find it in the compiled jar. If you are intrested in automaticly creating MANIFEST files for your bundles, have a look at the configuration of the org.apache.felix.maven-bundle-plugin in the pom.xml.

Detecting shape bundles

Like the ServiceTracker for tracking services, there is a BundleTracker for tracking bundles. A BundleTracker get's notified, when the state of bundles it wants to track change. Have a look at org.apache.felix.example.extenderbased.host.ShapeBundleTracker. The constructor defines, that only active bundles should be tracked. The addingBundle(Bundle bundle, BundleEvent event) method gets called by the framework, when a bundle enters the state activated. The tracker then checks, if the bundle headers contain the name property and if so, add the icon to the application.

Embedding the Framework

Since the R4 release the OSGi Framework provides facilities that allow an application to host it's own embedded framework instance. Therefore an implementation of the FrameworkFactory interface has to be used. OSGi implementors specify their FrameworkFactory implementation in the META-INF/services/org.osgi.framework.launch.FrameworkFactory file. Prior to Java 6, one had to parse the class name in that file by oneself. Luckily Java 6 has the ServiceLoader<S> class, that lets you easily instantiate a FrameworkFactoy. Have a look at the contents of the org.apache.felix.example.extenderbased.host.launch package in the extender-based host bundle (the implementation is the same for the service-based example).

The Application class is responsible for creating the framework and installing and starting the bundles. It uses a ConfigUtil for creating the framework configuration that is needed to create a framework using the FrameworkFactory. The ConfigUtil also creates a temporary cache directory for the framework. If the creation of the framework is successful, installAndStartBundles(String... bundleLocations) will be called to start the actual application. Therefor the Activator of the host bundle is instantiated. Note, that the host bundle can not register itself withing the framework it just created. Only the extension bundles will be registered within the framework.

As you can see no felix specific code is involved in any of the examples. That's one of the advantages of OSGi. Bundles that run on Felix will run on every other implementation of the same OSGi release.

Feedback

Subscribe to the Felix users mailing list by sending a message to [email protected]; after subscribing, email questions or feedback to [email protected].
    
        
        
            Change Notification Preferences
        
        View Online
        |
        View Changes
                |
        Add Comment
 ...
 In order to follow this example you need three things:
 # a [Subversion|http://subversion.apache.org/] client to check out the source code
# the IDE of your choice to view the source code
 # [Maven|http://maven.apache.org] to build the source code
 ...
 !example-application.png|align=center!
-h2. Service-Based Application on top of the Framework
+h2. Getting the source code
-Currently, the service-based example application is only available in our SVN repository. There are four separate projects that comprise the application, which can be found here:
+Currently, the example application is only available in our source control repositories. We have created two applications, one for the service and one for the extender-based approach. Both examples can be run as a bundled application on top of any OSGi implementation or by hosting an embedded framework. Assuming you are using svn to get the source code, you can find the source at the following locations:
 {noformat}
 ...
 http://svn.apache.org/repos/asf/felix/trunk/examples/servicebased.square 
http://svn.apache.org/repos/asf/felix/trunk/examples/servicebased.triangle
+http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.host 
http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.circle 
http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.square 
http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.triangle
 {noformat}
 ...
 {noformat}
-Once you have the projects checked out you can go into each sub-directory and build it using Maven; this assumes you have Maven properly installed. To build, simply perform the following in each project directory:
+h2. Building and running the examples
+Once you have checked out the projects you can go into each sub-directory and build it using Maven; this assumes you have Maven properly installed. To build, simply perform the following in each project directory:
 {noformat} 
mvn clean install 
{noformat}
 Once After you have built the projects, start Felix and then install/start the resulting bundle for one example (service or extender-based) from the {{target/}} directory of each project directory.
-Examine the source code to understand the details of the approach. In the future this documentation will hopefully be expanded to described more details.
+To start the examples using an embedded framework, export the jars you just build to a folder in your file system. 
Then start the host.jar and pass the names of all services/extensions to the application as parameters:
-h2. Service-Based Application embedding the Framework
+{noformat} 
java -jar servicebased.host-1.0.0.jar file:/servicebased.circle-1.0.0.jar file:/servicebased.square-1.0.0.jar file:/servicebased.triangle-1.0.0.jar 
{noformat}
-The host bundle from the previous section also implements the hosted framework service-based approach. The host bundle activator has a static {{main()}} method that creates an instance of Felix and loads the shape service bundles. The shape service implementations are the same for both the bundled and hosted framework application versions in this case. To execute the hosted framework application, issue the following command:
+If you are using an IDE like eclipse, you can run an embedded framework using a custom run configuration. In eclipse click _Run_ -> _Run Configurations..._ and create a new _Java Application_ run configuration. Select the host project you want to start (servicebased.host or extenderbased.host) and chose the {{Application}} class as _Main class_ from the org.apache.felix.example.servicebased/extenderbase.host.launch package. Switch to the _Arguments_ tab and fill in the following _Program arguments_ (assuming you want to run the extenderbased example):
 {noformat}
-java -jar target/servicebased.host-1.0.0.jar
+file:../extenderbased.circle/target/extenderbased.circle-1.0.0.jar file:../extenderbased.square/target/extenderbased.square-1.0.0.jar file:../extenderbased.triangle/target/extenderbased.triangle-1.0.0.jar
 {noformat}
-To successfully execute the hosted framework version of the application, you must be in the "servicebased.host" project directory when issuing the above command and you must have already built all of the other projects (i.e., circle, square, triangle).
+For more details on running an application with an embedded framework scroll down to the bottom of the page.
-Examine the source code to understand the details of the approach. In the future this documentation will hopefully be expanded to described more details.
+h2. Service-Based Application
-h2. Extender-Based Application on top of the Framework
+The service-based application uses the OSGi service concept and the service registry as the extensibility mechanism. Therefore the host bundle contains a service interface located at {{org.apache.felix.example.servicebased.host.service.SimpleShape}}. The SimpleShape service has two properties: a name and an icon. Beside that it defines one operation: {{draw(Graphics2D g2, Point p)}}.
-Currently, the extender-based example application is only available in our SVN repository. There are four separate projects that comprise the application, which can be found here:
+h3. Defining shapes as services
+Bundles that want to contribute a shape service have to implement the {{SimpleShape}} interface. Take a look at the circle bundle for example. The circle bundle only contains one class, the {{Activator}}. A {{[BundleActivator|http://www.osgi.org/javadoc/r4v43/org/osgi/framework/BundleActivator.html]}} is responsible for starting up a bundle. Therefore it gets passed in a {{[BundleContext|http://www.osgi.org/javadoc/r4v43/org/osgi/framework/BundleContext.html]}}, that can be used to perform registration of services within the framework. The {{Activator}} also contains a inner class that implements the {{SimpleShape}} interface and therefore represents the {{SimpleShape}} implementation of a circle. The {{start(BundleContext context}} method is used to register the circle implementation as a service:
 {noformat}
-http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.host 
http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.circle 
http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.square 
http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.triangle
+Dictionary<String, Object> dict = new Hashtable<String, Object>(); 
dict.put(SimpleShape.NAME_PROPERTY, "Circle"); 
dict.put(SimpleShape.ICON_PROPERTY, new ImageIcon(this.getClass().getResource("circle.png"))); 
m_context.registerService(SimpleShape.class.getName(), new Circle(), dict);
 {noformat}
-Check out each project using an appropriate SVN command, such as:
+First a {{[Dictionary|http://docs.oracle.com/javase/6/docs/api/java/util/Dictionary.html]}} is created to hold the service's properties. The two service properties are added to the dictionary. The icon of the circle service is located under src/main/resources/org/apache/example/servicebased/circle/circle.png. It gets loaded as an {{[ImageIcon|http://docs.oracle.com/javase/6/docs/api/javax/swing/ImageIcon.html]}} and added as icon property. The service then gets registered in the service registry by passing the name of the serivce interface, a service object and the service's properties.
-{noformat} 
svn co http://svn.apache.org/repos/asf/felix/trunk/examples/extenderbased.host 
{noformat}
+h3. Detecting shape services
-Once you have the projects checked out you can go into each sub-directory and build it using Maven; this assumes you have Maven properly installed. To build, simply perform the following in each project directory:
+The host's {{Activator}} creates a {{DrawingFrame}} for displaying the different shapes. It then delegates adding and removing of {{SimpleShape}} services to a {{[ServiceTracker|http://www.osgi.org/javadoc/r4v43/org/osgi/util/tracker/ServiceTracker.html]}} implementation. Then {{ShapeTracker}} gets notified, when a new {{SimpleShape}} service is added to, modified or removed from the service registry.
+h2. Extender-Based Application 
 
In contrast to the service-based example, the extender-based example uses bundles as it's primary extensibility mechanism. Therefore the host bundle containts a {{SimpleShape}} interface, that is much like the one from the service based example. It also containts a {{draw(Graphics2D g2, Point p)}} method and defines a set of properties. This time the properties are not used as properties for registering a service, but for defining bundle header properties, that can be read out from a bundles MANIFEST. 
 
h3. Defining shapes as extensions 
 
Bundles that want to contribute a {{SimpleShape}} extension have to implement the {{SimpleShape}} interface. Have a look at the extender based circle implementation for example. It only contains one class, {{Circle}}, that implements {{SimpleShape}}. Note, that in contrast to the service-based example there is no need to define a {{[BundleActivator|http://www.osgi.org/javadoc/r4v43/org/osgi/framework/BundleActivator.html]}}. This is because, there is no need to register a service within the framework. Information about the provided shape implementation is located in the bundle headers instead. Have a look at the circle's MANIFEST file:
 {noformat}
-mvn clean install
+Manifest-Version: 1.0 
Private-Package: org.apache.felix.example.extenderbased.circle 
Tool: Bnd-0.0.238 
Bundle-Name: Apache Felix Circle Extension 
Created-By: Apache Maven Bundle Plugin 
Bundle-Vendor: The Apache Software Foundation 
Build-Jdk: 1.7.0_01 
Bundle-Version: 1.0.0 
Extension-Class: org.apache.felix.example.extenderbased.circle.Circle 
Bnd-LastModified: 1331062969798 
Extension-Icon: org/apache/felix/example/extenderbased/circle/circle.p 
 ng 
Bundle-ManifestVersion: 2 
Bundle-Description: A simple extension for drawing circles. 
Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt 
Bundle-DocURL: http://www.apache.org/ 
Bundle-SymbolicName: org.apache.felix.example.extenderbased.circle 
Import-Package: org.apache.felix.example.extenderbased.host.extension 
Extension-Name: Circle
 {noformat}
-Once you have built the projects, start Felix and then install/start the resulting bundle from the {{target/}} directory of each project directory.
+As you can see, the three bundle properties, defined in the {{SimpleShape}} interface are set as bundle headers.
-Examine the source code to understand the details of the approach. In the future this documentation will hopefully be expanded to described more details.
+Note: The MANIFEST is generated by the maven build, so you will only find it in the compiled jar. If you are intrested in automaticly creating MANIFEST files for your bundles, have a look at the configuration of the [org.apache.felix.maven-bundle-plugin|http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html] in the pom.xml.
-h2. Extender-Based Application embedding the Framework
+h3. Detecting shape bundles
-The host bundle from the previous section also implements the hosted framework extender-based approach. The host bundle activator has a static {{main()}} method that creates an instance of Felix and loads the shape extension bundles. The shape extension implementations are the same for both bundled and hosted framework application versions in this case. To execute the hosted framework application, issue the following command:
+Like the {{[ServiceTracker|http://www.osgi.org/javadoc/r4v43/org/osgi/util/tracker/ServiceTracker.html]}} for tracking services, there is a {{[BundleTracker|http://www.osgi.org/javadoc/r4v42/org/osgi/util/tracker/BundleTracker.html]}} for tracking bundles. A {{BundleTracker}} get's notified, when the state of bundles it wants to track change. Have a look at {{org.apache.felix.example.extenderbased.host.ShapeBundleTracker}}. The constructor defines, that only active bundles should be tracked. The {{addingBundle(Bundle bundle, BundleEvent event)}} method gets called by the framework, when a bundle enters the state activated. The tracker then checks, if the bundle headers contain the name property and if so, add the icon to the application.
-{noformat} 
java -jar target/extenderbased.host-1.0.0.jar 
{noformat}
+h2. Embedding the Framework
-To successfully execute the hosted framework version of the application, you must be in the "extenderbased.host" project directory when issuing the above command and you must have already built all of the other projects (i.e., circle, square, triangle).
+Since the R4 release the OSGi Framework provides facilities that allow an application to host it's own embedded framework instance. Therefore an implementation of the {{[FrameworkFactory|http://www.osgi.org/javadoc/r4v42/org/osgi/framework/launch/FrameworkFactory.html]}} interface has to be used. OSGi implementors specify their {{FrameworkFactory}} implementation in the {{META-INF/services/org.osgi.framework.launch.FrameworkFactory}} file. Prior to Java 6, one had to parse the class name in that file by oneself. Luckily Java 6 has the {{[ServiceLoader<S>|http://docs.oracle.com/javase/6/docs/api/java/util/ServiceLoader.html]}} class, that lets you easily instantiate a {{FrameworkFactoy}}. Have a look at the contents of the {{org.apache.felix.example.extenderbased.host.launch}} package in the extender-based host bundle (the implementation is the same for the service-based example).
-Examine the source code to understand the details of the approach. In the future this documentation will hopefully be expanded to described more details.
+The {{Application}} class is responsible for creating the framework and installing and starting the bundles. It uses a {{ConfigUtil}} for creating the framework configuration that is needed to create a framework using the {{FrameworkFactory}}. The {{ConfigUtil}} also creates a temporary cache directory for the framework. If the creation of the framework is successful, {{installAndStartBundles(String... bundleLocations)}} will be called to start the actual application. Therefor the {{Activator}} of the host bundle is instantiated. Note, that the host bundle can not register itself withing the framework it just created. Only the extension bundles will be registered within the framework.
+As you can see no felix specific code is involved in any of the examples. That's one of the advantages of OSGi. Bundles that run on Felix will run on every other implementation of the same OSGi release.
 h2. Feedback
 ...