Blog from February, 2011

In my first two months at Talend I was mainly involved in building the first release of Talend Integration Factory (TIF). It is an Apache Licensed distribution of Camel with three interesting additions: A pre packaged OSGi container, an integration component for Talend Open Studio and some advanced examples. Let´s take a closer look at these addtions.

So why should you use Talend Integration Factory instead of Camel?

  • Synchronized Release Cycles: As the version number already suggests we are following the Apache Camel releases. So for each Camel release there will be a Integration Factory release shortly after. So unlike with other products you do not have to wait half a year for the new features to appear
  • No vendor lock in: The distribution is Apache Licensed so you can use it in almost any environment. We try to stay as near to the original Camel as possible. Bugfixes and Enhancements are directly committed back to Apache Camel and all other involved Open Source projects. In fact the current distribution did not need to patch Camel 2.6.0 as we got all our enhancements into the Camel Release.
  • Pre packaged OSGi container based on Karaf, Camel and CXF: OSGi is very interesting for central integration servers as integrations can be deployed without restarting the server. The integration artifacts are also much smaller then for typical .war deployments. To give a rough number a .war with Camel and CXf easily reaches a size of 20MB. A typical integration project in the OSGi container is only about 100KB in size. So while the benefits are clear many fear the complexity of setting up an OSGi environment so that Camel and CXF work as expected. As TIF Container prepackages all these things it is really easy to use. Still we were very careful to keep the container open. So you can easily upgrade all dependencies even without waiting for a new TIF release. The container also leverages all the features of Apache Karaf. So deployments are very easy and nicely integrated with your maven builds
  • Talend Open Studio integration: This component allows Talend Open Studio integrastions to participate in Camel routes. The component is the first step to a seamless integration with other Talend products
  • Advanced Examples: We have put together some examples that show use cases that are quite common in enterprise environments. More abbout these below

The examples show

  • jaxws_jms : Calling and publishing CXF JAXWS endpoints using Camel routes and JMS
  • jaxrs_jms_http : Calling and publishing JAXRS endpoints using JMS and HTTP over Camel routes
  • spring_security: Securing your integrations with Spring Security. Shows how to use Basic Authentication and @RolesAllowed annotations on the method level to secure CXF and Bean endpoints
  • claimcheck: This example shows some advanced DSL usages. The following EAI patterns are shown: Splitter, Claimcheck, Resequencer, Delayer

All examples are built with Maven. They and work standalone, in web containers and in OSGi. Each example is self contained so it can be easily copied and used as a temlate for your own projects.

Getting StartedWith this post I am beginning a series of posts about Apache Karaf, an OSGi container based on Equinox or Felix. The main difference to these frameworks is that it brings excellent management features with it.Outstanding features of Karaf:

  • Extensible Console with Bash like completion features
  • ssh console
  • deployment of bundles and features from maven repositories
  • easy creation of new instances from command line

All together these features make developing server based OSGi applications almost as easy as regular java applications. Deployment and management is on a level that is much better than all applications servers I have seen till now. All this is combined with a small footprint as well of karaf as the resulting applications. In my opinion this allows a light weight development style like JEE 6 together with the flexibility of spring applications.

Installation and first startup

  • Download Karaf 4.0.7 from the Karaf web site.
  • Extract and start with bin/karaf

You should see the welcome screen:

        __ __                  ____
       / //_/____ __________ _/ __/
      / ,<  / __ `/ ___/ __ `/ /_
     / /| |/ /_/ / /  / /_/ / __/
    /_/ |_|\__,_/_/   \__,_/_/

  Apache Karaf (4.0.7)

Hit '<tab>' for a list of available commands
and '[cmd] \--help' for help on a specific command.
Hit '<ctrl-d>' or 'osgi:shutdown' to shutdown Karaf.


Some handy commands

Shows all installed bundles
listShow user bundles
Shows the active OSGi services. This list is quite long. Here it is quite handy that you can use unix pipes like "ls | grep admin"
Shows exported packages and bundles providing them. This helps to find out where a package may come from.
Shows which features are installed and can be installed.
feature:install webconsole

Install features (a list of bundles and other features). Using the above command we install the Karaf webconsole.

It can be reached at http://localhost:8181/system/console . Log in with karaf/karaf and take some time to see what it has to offer.

diagShow diagnostic information for bundles that could not be started
log:tailShow the log. Use ctrl-c to  go back to Console
Ctrl-dExit the console. If this is the main console karaf will also be stopped.

OSGi containers preserve state after restarts

Please note that Karaf like all osgi containers maintains it´s last state of installed and started bundles. So if something should not work anymore a restart is not sure to help. To really start fresh again stop karaf and delete the data directory or start with bin/karaf clean.

Check the logs

Karaf is very silent. To not miss error messages always keep a tail -f data/karaf.log open !!

Tasklist - A small osgi application

Without any useful application Karaf is a nice but useless container. So let´s create our first application. The good news is that creating an OSGi application is quite easy and
maven can help a lot. The difference to a normal maven project is quite small. To write the application I recommend to use Eclipse 4 with the m2eclipse plugin which is installed by default on current versions.

Get the source code from the Karaf-Tutorial repo at github.

git clone

or download the sample project from and extract to a directory.

Import into Eclipse

  • Start Eclipse Neon or newer
  • In Eclipse Package explorer: Import -> Existing maven project -> Browse to the extracted directory into the tasklist sub dir
  • Eclipse will show all maven projects it finds
  • Click through to import all projects with defaults

Eclipse will now import the projects and wire all dependencies using m2eclipse.

The tasklist example consists of these projects

tasklist-modelService interface and Task class
tasklist-persistenceSimple persistence implementation that offers a TaskService
tasklist-uiServlet that displays the tasklist using a TaskService
tasklist-featuresFeatures descriptor for the application that makes installing in Karaf very easy

Parent pom and general project setup

The pom.xml is of packaging bundle and the maven-bundle-plugin creates the jar with an OSGi Manifest. By default the plugin imports all packages that are imported in java files or referenced in the blueprint context.

It also exports all packages that do not contain the string impl or internal. In our case we want the model package to be imported but not the persistence.impl package. As the naming convention is used
we need no additional configuration.


This project contains the domain model in our case it is the Task class and a TaskService interface. The model is used by both the persistence implementation and the user interface.  Any user of the TaskService will only need the model. So it is never directly bound to our current implementation.


The very simple persistence implementation TaskServiceImpl manages tasks in a simple HashMap. The class uses the @Singleton annotation to expose the class as an blueprint bean.

The annotation @Service will expose the bean as an OSGi service and the properties attribute allows to add serice properties. In our case the property service.exported.interfaces we set can be used by CXF-DOSGi which we present  in a later tutorial. For this tutorial the properties could also be removed.

    properties= {
		@ServiceProperty(name = "service.exported.interfaces", values = "*")
public class TaskServiceImpl implements TaskService {

The blueprint-maven-plugin will process the class above and automatically create the suitable blueprint xml. So this saves us from writing blueprint xml by hand.

Automatically created blueprint xml can be found in target/generated-resources
<blueprint xmlns="">
	<bean id="taskService" class="" />
	<service ref="taskService" interface="" />


The ui project contains a small servlet TaskServlet to display the tasklist and individual tasks. To work with the tasks the servlet needs the TaskService. We inject the TaskService by using the annotation @Inject which is able to inject any bean by type and the annotation @OsgiService which creates a blueprint reference to an OSGiSerivce of the given type.

The whole class is exposed as an OSGi service of interface java.http.Servlet with a special property alias=/tasklist. This triggers the whiteboard extender of pax web which picks up the service and exports it as a servlet at the relative url /tasklist.

Snippet of the relevant code:

@Service(classes = Servlet.class,
    properties = {
		@ServiceProperty(name = "osgi.http.whiteboard.servlet.pattern", values = "/tasklist")
public class TaskListServlet extends HttpServlet {
    @Inject @OsgiService
    TaskService taskService;
Automatically created blueprint xml can be found in target/generated-resources
<blueprint xmlns="">
	<reference id="taskService" availability="mandatory" interface="" />
	<bean id="taskServlet" class="">
		<property name="taskService" ref="taskService"></property>
	<service ref="taskServlet" interface="javax.servlet.http.HttpServlet">
			<entry key="alias" value="/tasklist" />

See also:


The last project only installs a feature descriptor to the maven repository so we can install it easily in Karaf. The descriptor defines a feature named tasklist and the bundles to be installed from
the maven repository.

<feature name="example-tasklist-persistence" version="${pom.version}">

<feature name="example-tasklist-ui" version="${pom.version}">

A feature can consist of other features that also should be installed and bundles to be installed. The bundles typically use mvn urls. This means they are loaded from the configured maven repositories or your local maven repositiory in ~/.m2/repository.

Installing the Application in Karaf

feature:install example-tasklist-persistence example-tasklist-ui

Add the features descriptor to Karaf so it is added to the available features, then Install and start the tasklist feature. After this command the tasklist application should run


Check that all bundles of tasklist are active. If not try to start them and check the log.


ID | Servlet         | Servlet-Name   | State       | Alias     | Url
56 | TaskListServlet | ServletModel-2 | Deployed    | /tasklist | [/tasklist/*]

Should show the TaskListServlet. By default the example will start at http://localhost:8181/tasklist .

You can change the port by creating aa text file in "etc/org.ops4j.pax.web.cfg" with the content "org.osgi.service.http.port=8080". This will tell the HttpService to use the port 8080. Now the tasklist application should be available at http://localhost:8080/tasklist


In this tutorial we have installed Karaf and learned some commands. Then we created a small OSGi application that shows servlets, OSGi services, blueprint and the whiteboard pattern.

In the next tutorial we take a look at using Apache Camel and Apache CXF on OSGi.

Back to Karaf Tutorials