On 06/11/2011 02:41 PM, Etienne Vrignaud wrote:
I understand that, but in my case, I am sure that the 3 bundles that I
have uninstalled were not used by any other bundle.
If a bundle is uninstalled and no one is using it then it will go away,
it only sticks around if someone is using it. You can "inspect p r"
(i.e., inspect package requirements) to see who is importing it.
And also my use case is simply reinstalling the same bundles after
having used them and uninstalled them.
I tried already to call PackageAdmin.refreshPackages() as mentioned in
the Bundle class documentation. But unfortunately, the Felix framework
request to stop. I cannot do that. I want to do live update without
restarting my product. Is there any way to refresh wiring without
stopping?
It will only request to stop if it is required by what you've
uninstalled (e.g., system bundle extensions). If you are just
installing/uninstalling normal bundles, then only those bundles and
bundles that depend on them will be affected by a refresh.
Otherwise what can I do in order to identify what's going wrong with the Wiring?
See the "inspect" command.
-> richard
2011/6/11 Richard S. Hall<[email protected]>:
It is valid to wire to uninstalled bundles since they still exist and it
might even make more sense to do so, since other bundles are obviously still
wired to the uninstalled bundle otherwise it wouldn't still exist. Wiring to
a different bundle will definitely partition the class space since some
bundles will be wired to the uninstalled bundle and newer bundles will be
wired to a different provider of the same packages.
If you want to avoid this, you must call PackageAdmin.refreshPackages() (or
"refresh" from Gogo) after uninstalling your bundles. That is the only way.
-> richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
