>One of the advantages of OSGI is supposed to be it’s ability to allow installation of modules without the need to restart a system. However, in eclipse, when ever you go through a P2 Update manager installation, it ALWAYS asks to restart eclipse. Reminds me of a Windows update procedure. I’d like it more like a Linux update….install and go…no restart.
-
Recent Posts
Category Cloud
Blogroll
Serenity
Archives
- September 2017
- June 2017
- May 2017
- January 2017
- May 2016
- November 2015
- August 2015
- June 2015
- April 2015
- March 2015
- February 2015
- January 2015
- December 2014
- October 2014
- August 2014
- July 2014
- June 2014
- April 2014
- March 2014
- February 2014
- January 2014
- December 2013
- September 2013
- August 2013
- July 2013
- May 2013
- April 2013
- March 2013
- February 2013
- August 2012
- March 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
Meta
intellectualcramps 
>This is a complicated problem and requires bundles to be “dynamic-aware.” The problem is that even though your bundle is dynamic aware, others in the system may not be and cause issues you don’t predict.This is also a provisioning problem in a sense that we currently have no way to determine if a bundle is dynamic aware. If we had something like a “Bundle-DynamicAware” true/false header, p2 could use this to determine whether to prompt or simply just to automatically apply the changes under the covers (or some other update strategy). The key here is that we have no way for bundles to properly identify themselves to be dynamic aware. Also, most bundles in the wild that use extensions or services aren’t dynamic aware completely as it’s a tough thing to do out of the box.
>@Chris:Yes, it would be very nice also to be able to qualify just how dynamic-aware a bundle is. For example, it is may often be the case that it is easier to process dynamic additions of extensions than to process dynamic removals. So, when disabling or uninstalling bundles, we could also determine whether a re-start is required.Oh, and of course, we’d like to specify which of a bundle’s extension points are dynamic in which dimensions.Never mind that there may be bugs in a bundle’s dynamic extension handling … 🙂
>For an application to be fully dynamic, the programming model is significantly more complex. For an IDE, I suspect that extra cost in development and maintenance is hardly justifiable. But there sure are many applications where it would make sense.
>This is one of the biggest disappointments for me. After all, the whole point of moving to OSGi in Eclipse 3.0 was to enable dynamic installation and uninstallation of plug-ins! But the problem is that the rules for being dynamic aware are not well understood, and there are just too many crap plug-ins out there.Frankly, in retrospect the ideal of a fully dynamic platform was always a pipe dream for something like the Eclipse IDE, where users tend to have a whole zoo of plug-ins of highly variable quality. Short of having some kind of certification system for plug-in authors, I don’t see this changing. However in more controlled environments like RCP applications, dynamic behaviour can still be a reality.
>For those who (like me) read these comments and have no idea what makes a plug-in dynamic, this appears to be an excellent starting-point:http://wiki.eclipse.org/FAQ_What_is_a_dynamic_plug-in%3F