In an recent interview, Eric Newcomer, IONA's CTO and co-chair of the Enterprise working group in OSGi, talks about his company's interest in OSGi, where he thinks OSGi will be going over the next few years, and why he thinks it has grown in popularity. Eric also has a few words to say on the relevance of OSGi to ESB and SOA, as well as whether or not Sun should become more interested in OSGi.
Facilitating the Spread of Knowledge and Innovation in Professional Software Development
Write for InfoQTopics
Helpful links
QCon London
Discover new ideas and insights from senior practitioners driving change in software. Attend in-person.
QCon San Francisco: Video-Only Pass
Video-Only Pass for professionally edited conference recordings.
The Software Architects' Newsletter
Your monthly guide to all the topics, technologies and techniques that every professional needs to know about. Subscribe for free.
Community comments
What is it with OSGi advocates
by William Smith,
Re: What is it with OSGi advocates
by Andrew Perepelytsya,
Re: What is it with OSGi advocates
by William Smith,
Re: What is it with OSGi advocates
by Neil Bartlett,
Re: What is it with OSGi advocates
by Eric Newcomer,
Re: What is it with OSGi advocates
by Mark Little,
Re: What is it with OSGi advocates
by Gerard Janssen,
What is it with OSGi advocates
by William Smith,
Your message is awaiting moderation. Thank you for participating in the discussion.
Sun and the members of the JCP are making a huge effort to ensure that it is compatible with OSGi, OSGi will support 277 (after all, 277 has 2 OSGi people on it). But it would be quite wrong for Sun to favour one vednor solution (OSGi) over all the others (Maven, Ivy, etc).
JSR-277 is a good thing for OSGi. It makes life easier from a JDK perspective for it and the other competing solutions. Bundles/modules become first class citizens on the JVM level. Beyond that, it’s up to the framework (OSGi or whatever else) to provide any value-add stuff they want to. 277 does not limit that. OSGi will offer proprietary extensions on top of the basic spec just like everything else in vendor land. So why do the OSGi people jump up and down all the time.
It would be rather like if the JBOSS folks were constantly attacking JPA because it didn't solely support hibernate.
Re: What is it with OSGi advocates
by Andrew Perepelytsya,
Your message is awaiting moderation. Thank you for participating in the discussion.
They attack JSR 277 not because it's coming from a JCP, but rather because the spec group blatantly ignored an 8-year experience OSGi brought us, and naively approached the problem with a "don't tell us how to do it, we know better" approach.
Isn't it the core idea of JCP to embrace industry experience and not reinvent a squared wheel?
Re: What is it with OSGi advocates
by William Smith,
Your message is awaiting moderation. Thank you for participating in the discussion.
I still don't get what the issue is.
Members of the JSR-277 expert group include two .NET experts, two OSGi experts who co-authored the R4 modularity spec, Maven's creator and Ivy's creator. Sonds like "embracing industry experience" to me, and exactly what the JCP is supposed to do.
Re: What is it with OSGi advocates
by Neil Bartlett,
Your message is awaiting moderation. Thank you for participating in the discussion.
William,
Take a look at the expert group mailing list for JSR 277, which is now open to the public (albeit read-only). Having done so, it's really hard to see that the two OSGi experts (Glyn Normington and Richard Hall) are being listened to. It's certainly not from a lack of effort on their behalf. There are numerous areas in the JSR 277 draft spec and the current strawman which are irreconcilable with OSGi: Sun is willfully refusing to learn any lessons from the experiences of OSGi/JSR 291.
OSGi people are not simply complaining because our favourite module system has not been chosen. That would be childish. The principle reason that we are making so much noise is that JSR 277 is heading towards failure as a module system! It will be hugely damaging to the entire Java community to have a broken module system baked into the JVM.
I would really like JSR 277 to be a success, but I believe that it should build on OSGi rather than compete with it. Competing APIs are great in some areas (e.g. GUI libraries or XML parsers) but the module system of the platform is not one of those areas. Can you think any other language or platform that has multiple competing module systems?
Neil.
Re: What is it with OSGi advocates
by Eric Newcomer,
Your message is awaiting moderation. Thank you for participating in the discussion.
By this logic OSGi should be encouraged to recruit JEE experts and define a better alternative to EJB.
Re: What is it with OSGi advocates
by Mark Little,
Your message is awaiting moderation. Thank you for participating in the discussion.
Plus it's wrong to say that "... t would be quite wrong for Sun to favour one vednor solution ..." Have you looked at who's involved with OSGi? Last time I looked it was more than a single vendor! With the exception of Sun, I think all of the usual major JEE suspects are there.
Re: What is it with OSGi advocates
by Gerard Janssen,
Your message is awaiting moderation. Thank you for participating in the discussion.
That's right! Without wanting to oversimplify the issue here. It seems like yet another round of Sun playing the "not invented here" game. Ever since I got acquainted with OSGi it seemed to me like it had solved so many questions of component models, component dependency checking, deployment and upgradeability that most appserver vendors have not yet solved properly and that the official jee standards are not even touching at all.