Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 333193 - Framework hooks should allow bundles to be installed in any region using BundleContext.installBundle
Summary: Framework hooks should allow bundles to be installed in any region using Bund...
Status: CLOSED FIXED
Alias: None
Product: Virgo
Classification: RT
Component: runtime (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.0.0.M01   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 333189
Blocks: 330776
  Show dependency tree
 
Reported: 2010-12-24 07:28 EST by Glyn Normington CLA
Modified: 2011-02-04 09:59 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Glyn Normington CLA 2010-12-24 07:28:05 EST 
Currently, there is no good way to decide which region a bundle should belong to, so a static approach is taken where the first few bundles installed comprise the kernel region and any installed subsequently comprise the user region. This does not allow bundles to be added to the kernel region after the user region has been created and it does not allow multiple user regions to be implemented.

This requires a bundle install hook which will allow a bundle being installed to "inherit" the region of the bundle doing the install. See Equinox bug 333189.

Of course, a special purpose API could be used to approximate the required behaviour, but this would be race-prone as BundleContext.installBundle adds the new bundle to the framework's collection of bundles before returning. So the new bundle could be passed to the framework hooks, such as the bundle find hook, before it has been associated with its region.
Comment 1 Glyn Normington CLA 2011-02-04 09:59:01 EST 
This was implemented using the bundle event hook.