Page History

...

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

...

Transparent composite model

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

4.2.1

...

Transparent composite description

Extended Transparent composite bundles can require bundles using the following header:

...

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 transparent composite bundle lifecycle, more details will be present in the next section.

4.2.2

...

Transparent composite lifecycle management

To provide access to constituent bundles into the parent framework, the extended composite manager must proxy provided constituent bundles as separate virtual bundles in the parent framework. This complicates lifecycle management since it creates separate points of control for the composite bundle and it also complicates maintaining class space consistency for clients of the provided bundle. This section discusses these issues in more detail.

...

Performing individual lifecycle operations on the proxied bundles should function like normal in the parent framework, but should have no impact on the internals internal constituent bundles of the composite. For example, you can start, stop, and even uninstall provided bundles, but this just impacts the state of the bundles in the parent framework, which may render them unresolvable.

...