Page History

...

The simple composite model fits fairly well within the constraints of the OSGi framework since it aligns fairly well with the concepts embodied in the original OSGi specification (i.e., packages and services). However, some use cases may require support for beyond these original concepts. For such cases, this proposal defines the extended composite model as an extension of the simple composite model that includes additional support for provided and required bundles at the expense of added complexity.

4.2.1 Extended composite description

Extended composite bundles can require bundles using the following header:

• Require-Bundle - the bundles required by the composite from the parent framework.

The composite manager makes the required bundles available to the composite bundle's constituent bundles. A new header is defined to provide access to constituent bundles in the parent frameworkThis proposal introduces one final header, which is:

• Provide-Bundle - a comma-delimited set of symbolic names specifying the constituent bundles provided by the composite bundle to the parent framework.

The provided bundles will be manifested in the parent framework as virtual bundles themselves. This means that in addition to the composite bundle in the parent framework, there will ultimately be additional virtual bundles installed by the composite manager for each provided bundle; since this is related to the extended composite bundle lifecycle, more details will be present in the next section.

4.2.2 Extended composite lifecycle management

...