Java Development News:
OSGi: Not Easy Enough to Use. Not as Productive as it Should Be
20 Jun 2011 | TheServerSide.com
SpringSource's Rod Johnson on OSGi
The following is a partial transcript of the conversation TheServerSide's Cameron McKenzie had with the creator of the Spring framework, Rod Johnson. In this part of the conversation, Rod speaks about how SpringSource positions itself with regards to OSGi technology.
We have changed our views on OSGi over the years
Ease of Use and Productivity
"We have changed our views on OSGi over the years, and one of the reasons for that is that OSGi simply cannot be made as easy to use and as productive as we feel is consistent with Spring values.
Niche technology vs. the mainstream...
"OSGi is a perfectly good technology but over time we’ve come to the conclusion that it’s really a niche technology rather than a mainstream technology. For example, OSGi’s fantastic if you’re building a very platform specific environment where you’re kind of assembling your own servers that have an unusual footprint. OSGi is great for that.
The best way to use OSGi...
The benefit that most users want is a server that has a really small memory footprint, good management, fast startup time...
"OSGi is also great for dynamic redeployment. So the Spring DM Server product that we took to Eclipse as Virgo, if you want to use OSGi, this is the best way to do it.
"What we found in the server space, is frankly, TC server is a much better fit for what people want. It doesn’t have the advanced module system, but it’s got an incredibly small footprint. The benefit that most users want is a server that has a really small memory footprint, good management, fast startup time,and you can get those things without the complexity of OSGi."
-Rod Johnson, SpringSource/VMWare