Treading into OSGi

On my current project, the number of JavaBeans / Spring Beans is becoming a bit too much to handle. What’s becoming quite painful is that there is a significant number of combinations and dependencies between beans, and between the various web applications that we are rolling out. Simply including a few “common” JARs in multiple WAR’s is not good enough anymore.Modularity and dynamic modules has always been painful in Java, mostly due to its ridiculous class loader. But OSGi seems to offer significant improvements in this area.  The possibilities of having classes “plugging” into each other, resolving versions, etc., all dynamically is terribly exciting and, at the same time, frightening.Nevertheless, I will be venturing into OSGi land and will blog my experiences and hopefully provide a some simple HOWTO’s and tutorial style posts.

One thought on “Treading into OSGi

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s