Page History

...

• Large application subsystems can be modeled as a composite bundle.
• Different applications running in the same framework instance can be isolated from each other inside of composite bundles.
• Web Application servers could model EARs and composite bundles to isolate inner libraries while allowing sharing from the server.
• Groups of bundles needing lifecycle management as a whole can be modeled as a composite bundle.

...

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 :

1. A simple composite model that supports only package and service sharing.
2. A transparent composite model that extends the simple composite model with bundle sharing.

NOTE 1: The purpose is not to actually treat the two models as separate entities, but to more clearly illustrate the extra cost in complexity by supporting transparency.

NOTE 2: Although this document is API-less, the and extending this model to support additional scenarios at the expense of making it more complicated.NOTE: The goal is not to completely rule out any API, but to keep things simple until some real-world experience is gained at which point API could potentially be introduced.

...