Community
Participate
Working Groups
In light of bug 326502, we should review how PDE updates and resolves its OSGi state when bundles are removed/added/changed. Not clear if the change for bug 326011 is a breaking behavior change, or if PDE should update it's use of the resolver API.
Let me give my POV. The resolver should be least perturbing by default. When a bundle description which other descriptions are wired to (imported packages, required etc.) is updated then the resolver should not automatically flush the old bundle description when you call the State.resolve(BundleDescription[]) method. These old versions of descriptions are in the "removal pending" state. We are waiting for someone to call State.resolve(BundleDescription[]) with a description that has the same id (long) as the description that is "removal pending. This method is telling the state to re-resolve the BundleDescriptions passed and flush out any old versions of the BundleDescriptions which have the same id (long) as the descriptions passed in. While working on bug326502 I noticed that the resolver implementation would automatically flush all removal pending descriptions no matter what array was passed to State.resolve(BundleDescription[]). At runtime this behavior can be quite unexpected if an operator is trying to delay a refresh of the system until an appropriate time. Aggressively flushing the removal pending descriptions takes any control that the operator may have had to control down time of the system. I think that PDE should keep track of all descriptions it not only adds but also passes to State.updateBundle and call State.resolve(BundleDescritpion[]) with all descriptions that have been modified or added to the state.
(In reply to comment #1) > While working on bug326502 ... The correct bug is bug326011
*** Bug 182951 has been marked as a duplicate of this bug. ***
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Please reopen if this still needs to be considered.
