The AriesSubsystem service has the addRequirements method that dynamically updates the import sharing policy but nothing for capabilities. I suppose we could add something but a big question would be how much responsibility lies with the implementation and how much with the user. The simplest approach impl-wise would be to allow the export sharing policy to be updated. The user would be responsible for everything else. I think the flow would be update bundle -> update sharing policy -> refresh bundles?
On Wed, Sep 23, 2015 at 11:05 AM, David Bosschaert < [email protected]> wrote: > Hi all, > > I was wondering about the following scenario and how this can be done > in Aries Subsystems. > > Let's say you have a composite subsystem that exports some packages. > Now at some point in time you update a bundle inside that composite > subsystem and now it exports another version of a package that it > previously exported, or maybe even a totally new package. > > In such a case I would really like to change what the composite > subsystem exports. > The OSGi subsystem spec does not (yet) define an update() operation > but is something like this somehow possible with the Aries > implementation? > > Thanks, > > David >
