Skip to main content

(NOT) yet Another Getting Started with OSGi

Last week I have been learning OSGi.

I got my first application running in OSGi. I am not going to write another getting started post with code that will show a hello world. But rather give you an idea how to start getting in the mud. And then may be show you more than a direction :)

I used Equinox 3.4 (OSGi R4) implementation. I prefered it over Felix. Why - Eqinox is simple, and a single jar download. But I guess that aint a thing to notice. You can get Equinox jar from here. If the link is broken, go here, download the equinox framework, it should be ~0.95MB.

Start equinox framework as
java -jar equinox.jar -console
You would have seen this on a lot of sites. but I did fall on two things flat on my face; missing -console and doing it wrong --console :P

As per the spec, (and by now, you know) a bundle is a jar with some special informtion in MANIFIEST.MF. A Bundle jar need not DO anything. It could just sit installed or be active (by exporting packages and services). So if you have a jar with just one interface that defines a static final variable: It can be jar-ed to a bundle too. It may not do much (other than exposing the constant). but it is a Bundle.

And then, There is a starter interface is BundleActivator. No I am not writing Hello World program. This interface can be used by adding
Import-Package: org.osgi.framework
manifest header(mind the space after the colon). Along with that, You need to point (only one) a class that implements this interface (start() and stop()) to handle the call backs by adding
Bundle-Activator: fully.qualified.class.name.of.HelloWorldBundleActivator
That gives you enormous power to do a loooot of things in OSGi. You are now literally the master of the universe (or atleast of the framework instance :P). Because with these two hooks (callback methods) you can traverse through the BundleContext. The BundleContext(, like ServletContext) exposes you to a lot of things around you. The framwork, The bundles living with you, Thier metadata, Their statuses, mechanism to programatically do stuff..

errr.. its 22:10, I gotta go to bed now.. If you want to learn more, Dont download a book. Start with the code. You can figure? Start with this one. I will see you in the next post..

Popular posts from this blog

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>