Ok that sounds good. I simply cannot find a reason to do prepare for bundleprocessor yet :-)
Continue our discussion on Aries-283: I wonder if we want the user to separate the subsystem-content and subsystem-resource. With existing application code, I think the content and resource are all in the content, and it is the underlying code to decide if a convert is needed. This may make users job a bit simpler. For example, for a war file, the user doesn't have to know/care that it needs to be converted, and can specify it in the subsystem-content. Regarding VersionRange for Resource, I think it makes sense to have some SubsystemMetadata interface that represents the initial metadata for the subsystem and in that the subsystem content can be version ranges. For Resource, since it is the best match found by the resource resolver and the one we'll install, it makes sense to have a fixed version for it, like what we have today. WDYT? Lin On Thu, Apr 15, 2010 at 9:24 AM, Guillaume Nodet <[email protected]> wrote: > > Actually, there may be some use cases for the prepare() method. > The reason is that when installing a subsystem, a processor may be > called multiple times for different resources, yet, a single session would > be used. The prepare() would then allow some processing after all > resources have been processed. > > If you look at the subsystem processor, it actually restarts the subsystems > that were previously stopped (during an update for example). Restarting > those > in the process() method could have undesirable effect such as forcing the > resolution > of some bundles too early. > > So we may want to keep it ...
