OSGi – The Missing Piece Of The Jigsaw
Recorded at:
OSGi for web application
by
Daniel Joseph
Re: OSGi for web application
by
Richard Vowles
Re: OSGi for web application
by
Han Meng
1. Modular
2. Dynamic, for this, it includes several meanings, pluggable service, replace and update service without stopping whole application.
3. Extensible
Re: OSGi for web application
by
Marc Sch
I am imagining a osgi-web-application which has a special bundle that is stopped by default. Once it gets started it will display a message on each page to the user, letting him know that an update of the system will occur soon and that some services might not be available for a short while (updating in OSGi is quick).
When the update occurs the relevant services will be shut down and the consuming bundle has to deal with that, meaning that the user will be presented a message that the service he is trying to acces is curerntly not available. When the service is back everything continues as usual and the update-notifier-bundle can be stopped (until the next release).
This is just a quick idea without putting much time into the details ;)
As Ian states out, having the application handle services going away is cumbersome, and it will be interesting to see how these blueprint-containers will help at this point.
I personally cant wait to try out these WTP plugins...but I should get some rest first :-D
Btw: for me, this is one of the best summaries on OSGi-technology I've found until now. Hope to hear/see more from Ian




Hello stranger!
You need to Register an InfoQ account or Login to post comments. But there's so much more behind being registered.Get the most out of the InfoQ experience.
Tell us what you think