Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 254021 - Implement CompositeBundles (rfc 138)
Summary: Implement CompositeBundles (rfc 138)
Status: RESOLVED FIXED
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.5 M5   Edit
Assignee: Thomas Watson CLA
QA Contact:
URL: http://www.osgi.org/Download/File?url...
Whiteboard:
Keywords:
Depends on:
Blocks: 247354
  Show dependency tree
 
Reported: 2008-11-05 17:40 EST by Thomas Watson CLA
Modified: 2009-01-19 17:14 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Watson CLA 2008-11-05 17:40:26 EST
RFC 138 defines a new FrameworkFactory service which allows for the creation of child frameworks and also provides a means of linking two frameworks which can be used to share packages and services from a source framework to a target framework.
Comment 1 Thomas Watson CLA 2008-11-05 17:41:54 EST
Targeting M4.  I have been prototyping this feature for a while now.  I plan to release an initial implementation soon.
Comment 2 Thomas Watson CLA 2008-11-10 18:44:20 EST
I was close to releasing an implementation of 138 but we decided to significantly change the API for creating child frameworks and how to share packages and services with them.  We should have the API locked down this week and hopefully have an implementation before M4 is done.
Comment 3 Thomas Watson CLA 2008-12-08 09:20:14 EST
This is slipping to M5.  I have an initial implementation done, but it needs to be cleaned up.  The API is likely to change.  I do not want to release a half-baked implementation with an API that is likely to change into M4.  I plan to release the initial implementation into M5 before the end of the year.
Comment 4 Thomas Watson CLA 2008-12-08 09:37:24 EST
OSGi is currently calling these LinkBundles.  I really want to change the name the CompositeBundles.  The concept seems to fit well for me.  We have a bundle composed of 1..n bundles that happen to be running in a child framework.  The composite can import/export resources to/from the composite bundle.
Comment 5 Thomas Watson CLA 2008-12-16 11:39:23 EST
The name of the API has been changed to CompositeBundle and CompositeBundleFactory.  We have also introduced another bundle type (SurrogateBundle) which represents the composite inside the child framework.  I have released a rough implementation of the new API into the RFC138_work branch.

I will continue to polish the code in this branch and hope to release the code to HEAD before the first I-Build in January.
Comment 6 Thomas Watson CLA 2008-12-19 17:39:41 EST
I released the latest code from the branch into HEAD.
Comment 7 Thomas Watson CLA 2009-01-19 17:14:45 EST
Marking as fixed for M5.  Additional changes may come to the API in M6.  Also note that the composite bundles specification will be made a "proposed" specification for the OSGi R4.2 release.  This means from an Eclipse perspective the API for composite bundles is provisional (internal) and not real API.