Felix Meschberger <[EMAIL PROTECTED]> writes: > 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.
This is interesting. The "set bundle" refers to the other bundles not in the abstract (by exported packages), but as concrete references to symbolic name and version. It sounds kind of like the Require-Bundle header. Is there a reason why you don't use Require-Bundle, other than it not having been implemented in Felix until recently? Does the "set bundle" start all its related bundles when it itself is told to start, and stop all the others when it stops? Do you deploy this "set bundle" through OBR? If so, it sounds like the "set bundle's" bundle associations aren't known to OSGi (being specified by this special header you mention above), so how do the associated bundles get discovered through OBR? Or does the "set bundle" itself use OBR to deploy all its associated bundles? > 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. I see. Thanks for clarifying. -- Steven E. Harris
