There has been some buzz on OSGi’s usability. This was always an issue, but the topic was renewed with some comments by the Spring Framework people.
I wonder if all this indicates is that SpringSource is working on or has a competitor to OSGi? In the past some companies have disparaged certain technologies or approaches, but then embraced them, for example, IoC and ESB. Seems unlikely, from available links, they claim to still be supporting the Virgo server and other OSGi efforts.
But, since SpringSource created an OSGi server (and later donated to Eclipse foundation) and some extensions to OSGi, they would be in a good position to see what an application developer would need in a modularity solution.
My personal take on the issue? I tried OSGi a few times, hand creating the manifests. It was complex. I don’t know why someone can’t just create a GUI based tool to do this (for non-Eclipse based apps). Just drag a jar onto the tool, then drag and click to do the OSGi magic.
Do we really need modularity? I guess those who critique this have not been confronted with Jar hell. Even in a single tier simple application, once you start using third-party libraries, you are in danger of that dreaded linear classpath.
— Rod Johnson’s followup
— Ease of Use and Spring
— OSGi: Not Easy Enough to Use. Not as Productive as it Should Be
— the need for modularity
— SpringSource to move dmServer to Eclipse – OSGi not ready for mainstream?
— dm Server project moves to Eclipse.org