Read the article: OSGi: A Proven Approach for Modular Development
Rod Johnson's comments on the applicablilty of OSGi created a firestorm of comments and interest from TheServerSide (TSS) community, prompting TSS to start digging deeper into the technology and search out the insights of some of the industry's experts. The current plan is to corral a series of article on the topic, from both the detractors and advocates of the technology, while throwing in a useful tutorial and expert tip on the subject when the timing is right.
The first salvo in this OSGi discussion comes from Peter Kriens of the OSGi alliance, as he provides some background on the history of OSGi, and some insights on why an uninitiated Enterprise Java developer might initially have some reservations when looking at how OSGi tackles the topic of modularity.
Of course, the preamble of the article is simply an appetized, whereas the ensuing discussion about indirection, loose coupling and the deficiencies of the Inversion of Control (IoC) mentality is the meat. Pontificating on the manner in which IoC frameworks like Spring achieve their end goals, Peter states the obvious when he says: "The problem is that IoC requires us to give up control in our code, the only place where we actually have full knowledge of the internal details."
Indeed, that always has been one of the more peculiar curiosities about how modern applications are developed. Inversion of Control often seems more like an application has lost control. But does the OSGi approach have the capacity to address this devilish little detail of IoC? Peter is confident that OSGi unequivocally does.
You can read Peter's insights into the topic here: