Win a copy of Clojure in Action this week in the Clojure forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

OSGi Myths

 
Craig Walls
author
Ranch Hand
Posts: 363
8
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As I answer questions this week, I find that there are a few misconceptions about OSGi. I'm not terribly surprised...I was encountering those same misconceptions several months ago when I blogged this: http://www.jroller.com/habuma/entry/a_dozen_osgi_myths_and

I just thought I'd throw this blog entry out here for you to read in case you've not seen it before. I'm thinking about writing a "More OSGi Myths" blog sometime soon that will likely include things like "OSGi is just a remoting technology like SOAP or RMI" or "OSGi is just another way of doing EJBs".

If any of you have any beliefs or thoughts about OSGi that you think may fit into the OSGi Myths category, I'd love to hear them so that I can add them to my list.
 
Marco Ehrentreich
best scout
Bartender
Posts: 1294
IntelliJ IDE Java Scala
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Craig,

thanks for the link to your very interesting blog. It seems that one knows almost anything important about OSGi after reading the answers to the myths

Unfortunately or luckily I can't think of any other myth I've come across at the moment .

Marco
 
Hong Anderson
Ranch Hand
Posts: 1936
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for the useful resource. Anyway, if myths mean untrue stories or false beliefs, I disagree with this "I can get modularity without OSGi".
I just disagree on the fact that it's included in Myth list, whereas it's not a myth, it's a truth that we can get modularity without OSGi and you also stated that in the explanation.

And about "OSGi is for Eclipse users", I don't think so. I think the myth should be "OSGi is for Eclipse plug-in developers" or "OSGi is for Eclipse-based application developers".
Because most of "Eclipse users" have nothing to do with OSGi, most of them don't know what Eclipse really is, what Eclipse is based on, and architecture of Eclipse, let alone OSGi.
 
Hong Anderson
Ranch Hand
Posts: 1936
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think the followings might be qualified as OSGi Myths (or not):
- OSGi is for desktop applications.
- OSGi is useful for applications that use plug-in architecture.
- Dynamic Updates feature of OSGi is a lie, I'm using Eclipse which uses OSGi, but after updated some plug-ins, I had to restart Eclipse to make it works properly (Maybe this one is too long).
 
Craig Walls
author
Ranch Hand
Posts: 363
8
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Kengkaj Sathianpantarit wrote:I think the followings might be qualified as OSGi Myths (or not):
- OSGi is for desktop applications.


Good one...actually this could be changed to say "OSGi is only useful for XXX applications (where XXX could be any finite class of applications)".

In fact, OSGi is good for a broad selection of application types, including desktop, web, integration, application server, etc, etc. You name it. Anywhere that can benefit from more modularity is a good place to consider OSGi.

- OSGi is useful for applications that use plug-in architecture.


Kinda the same thing, but a bit more specific. It's true that OSGi provides a lot of the plumbing necessary to support plugins, but that's not all it's good for. It just so happens that's how the Eclipse IDE takes advantage of OSGi. The other benefits of modularity are actually much more interesting, even if you don't care about plugins.

- Dynamic Updates feature of OSGi is a lie, I'm using Eclipse which uses OSGi, but after updated some plug-ins, I had to restart Eclipse to make it works properly (Maybe this one is too long).


Right...I've heard this one before. Actually, the reason you have to restart eclipse after a plugin update has little to do with OSGi and much to do with the legacy of Eclipse plugins. (And, even though Eclipse requests that you restart, sometimes it still works if you don't.) The details of this are far beyond the scope of this forum response...but if I ever write that 2nd set of myths, I'll be sure to explain it a bit more there.
 
Craig Walls
author
Ranch Hand
Posts: 363
8
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Kengkaj Sathianpantarit wrote:Dynamic Updates feature of OSGi is a lie, I'm using Eclipse which uses OSGi, but after updated some plug-ins, I had to restart Eclipse to make it works properly (Maybe this one is too long).


The timeliness of this blog entry is perfect: http://eclipsesource.com/blogs/2009/07/23/osgi-dynamics-and-eclipse/

This blog entry explains better than I possibly can why OSGi is dynamic, but Eclipse's plugin system may not be as dynamic. In short, there are legacy reasons why the Eclipse plugin system isn't as dynamic as OSGi itself is...and there's the matter of writing plugins (or any OSGi bundle for that matter) in such a way that they support dynamic updates.
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic