Why OSGi? Or why not using it makes your JVM runtime unsafe.
Updated: 2012-04-30 19:28:09
. var log mind Dhananjay Neneâ s opinions on programming , design , architecture and the internet RSS Blog Archives About Why OSGi Or Why Not Using It Makes Your JVM Runtime . Unsafe Jan 21 st 2012 Comments Not sure how long ago I started using OSGi . Perhaps it was 12 months ago or then perhaps 18. And yet I still find it painful using OSGi especially every time I bring in a foreign set of jars into the ecosystem . And yet I continue to be a dogged proponent . Hereâ s . why First let us understand one of the many problems OSGi solves . Let us imagine your java application has exactly three classes . One is the class you wrote called âMy.javaâ bundled in a jar called âmy.jarâ . Another is a class called âUses.javaâ whose api and features are leveraged by âMy.javaâ and is

K . Scott Allen Experiments In Writing Home A Refactoring Experiment Soon I'll be giving a group of developers some code and asking them to do some refactoring . The bad news is the code is hard to read . Some might say it's intentionally obfuscated , but let's not assume malice right away . The good news is there are six working unit tests for the code . There are two goals to the exercise . One goal is to give developers an opportunity to practice refactoring a Kata , if you will The way I'd attack the code is to start with some renaming operations , then extract some methods , then perhaps break down the one big class or eliminate a switch statement using a patterns . There is no perfect . answer The larger goal is to convince anyone not entirely sold on the benefit of automated tests