...

• Composite bundle - a bundle whose contents is actually a set of bundles that appear to be running inside of another framework instance.
• Constituent bundle - the bundles composing a composite bundle.
• Parent framework - the framework in which a composite bundle is installed.Composite framework - the framework running inside the composite bundle (this term may not be necessary)
• Required bundle - a bundle required by a composite bundle from the parent framework.
• Provided bundle - a constituent bundle from a composite bundle made available in the parent framework.

4. Technical approach

The overall technical approach is to use the virtual bundle concept (proposed separately) to manage composite bundles as a layer above the framework. This proposal forgoes an API-based approach to support a simple, declarative approach. The technical approach is divided into two halves for supporting a more simplistic composite model and extending this model to support additional scenarios at the expense of making it more complicated.

...

Since the composite manager manages all aspects of the composite's content, its active lifetime scopes its managed composites. In other words, if the composite manager is stopped, then it explicitly causes all of its managed composites to refresh and return to the installed state.

4.2 Extended composite model

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

...