Re: [p2-dev] Starting bundles programatically without restarting the sys

[Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>]

The code in org.eclipse.equinox.simpleconfigurator.ConfigApplier#install does not restart all the bundles. It will only uninstall, install and start the bundles that have changed. However depending on the bundles you are updating and the wiring between all the bundles of the system, more bundles will be stopped, rewired (classloading dependency) and restarted. This is how OSGi works (see the PackageAdmin#refreshPackages). For example if you were to replace the eclipse extension registry in your SDK you would take most of the system down because of its central role, however if for example you are just installing a new SCM provider you don't have to restart the system.
HTH


Saminda Wijeratne ---07/30/2009 06:31:43 PM---Hi,

From:	Saminda Wijeratne <samindaw@xxxxxxxx>
To:	p2-dev@xxxxxxxxxxx
Date:	07/30/2009 06:31 PM
Subject:	[p2-dev] Starting bundles programatically without restarting the system

---

Hi,

We have successfully integrated p2 to our wso2 products. We are now trying to see whether it is possible to hot install the features. i.e. once through p2 the feature is installed without restarting the equinox framework is it possible to programatically start the new bundles. Can this be done in current implementation? a workaround perhaps? 

I've debugged through the existing ui code in Galileo and found the following code 
           Configurator configurator = (Configurator) ServiceHelper.getService(Activator.getContext(), Configurator.class.getName());
           configurator.applyConfiguration();
I've included and tried the above code but seems to stop and start all bundles in the system rather than only the new ones. Any suggestions would be helpful.

Thanks in advance,
Saminda_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev