Composing applications with karaf features http://steinar.bang.priv.no/?p=310 #apache_karaf #java_programming #declarative_services #derby #jdbc #karaf #liquibase #osgi #osgi_services #paxjdbc #paxjdbcconfig #postgresql I create web applications by first creating a set of OSGi bundles that form the building blocks of the application, and then use karaf features to pull the building blocks together to create complete applications that run inside apache karaf. The bundles are (in order of initial

My OSGi story http://steinar.bang.priv.no/?p=306 #apache_karaf #Eclipse #java_programming #declarative_services #eclipse #karaf #osgi #osgi_services OSGi is a Java plugin framework and module system that were initially created for supporting embdedded applications in the automotive industry. OSGi also forms the foundations for the Eclipse IDE plugin model. The plugin model of OSGi consists of components waiting for services and starting and exposing services when all of the dependencies are sat

Rewriting applications to use pax-jdbc-config and liquibase http://steinar.bang.priv.no/?p=292 #apache_karaf #java_programming #declarative_services #derby #jdbc #karaf #liquibase #osgi #osgi_services #pax-jdbc #pax-jdbc-config #postgresql After creating the post Pluggable databases for apache karaf applications I posted a link to the blog post in the karaf user mailing list, and the immediate response was, “why didn’t I just pax-jdbc-config instead?“. The answer to that is that I didn’t know a

Pluggable databases for apache karaf applications http://steinar.bang.priv.no/?p=265 #apache_karaf #java_programming #declarative_services #derby #jdbc #karaf #liquibase #osgi #osgi_services #pax-jdbc #postgresql Edit: I no longer use this approach. I use pax-jdbc-config instead.  See the article Rewriting applications to use pax-jdbc-config and liquibase for details When creating databases for my apache karaf based web applications, I want the following things: A database-independent schema cr