Hi, On 2/10/07, Steven E. Harris <[EMAIL PROTECTED]> wrote:
Felix Meschberger <[EMAIL PROTECTED]> writes: > In fact we do exactly this at our place: Define bundle sets and have > a management agent control the lifecycle What defines a set of bundles? Is it their symbolic names?
Actually, the bundle set descriptor is a bundle itself, which has a special manifest header naming other bundles (or resources in OBR speak) to be managed. The reference is by bundle symbolic name and a version range.
and just use OBR to get the bundles in the first place and make sure > any required bundles are also retrieved. How do you know which bundles were retrieved? Are you using Resolver.getRequiredResources()? If so, how do you get from a Resource to a Bundle?
I check the Resolver.getAddedResources(), Resolver.getRequiredResources() and Resovler.getOptionalResources(). For each of the resources I take its symbolic name and version to find the matching bundle - through PackageAdmin as Richard notes in another mail or simply looping through the bundles. Also, do you worry about controlling the life-cycle of the required
bundles that weren't part of your original set? That is, if your bundle set A contains bundles "foo" and "bar", but "bar" turns out to require "baz", do you add "baz" to set A's life-cycle operations?
No, "baz" is just started and assigned a startlevel which is equal to the lowest startlevel of any of the bundles contained in the set. Regards Felix
