Hi Carsten, You can't do this via the Subsystem manifest. The manifest is a provisioning list and to change that list requires a new manifest. You can do this programmatically through the subsystem API using the region context bundle. Runtimes can provide operational support for doing this. For example, the OSGi application support in WebSphere allows you to operationally add/remove composites to/from a running application.
Regards, Graham. Graham Charters PhD CEng MBCS CITP STSM, WebSphere OSGi Applications Lead Architect, Master Inventor IBM United Kingdom Limited, MP 146, Hursley Park, Winchester, SO21 2JN, UK Tel: (Ext) +44-1962-816527 (Int) 7-246527 (Fax) +44-1962-816527 Internet: [email protected] From: Carsten Ziegeler <[email protected]> To: OSGi Enterprise Expert Group Mail List <[email protected]>, Cc: "[email protected]" <[email protected]> Date: 26/05/2014 07:24 Subject: Re: [eeg] Subsystems: hotfix workflow Sent by: [email protected] Hi, what do you do if the update to a subsystem contains a new bundle? Updating/Removing bundles within a sub system should be doable via the framework API - but adding a bundle to a subsystem? Regards Carsten -- Carsten Ziegeler | Adobe Research Switzerland | www.adobe.com [email protected] +49 151 163 063 24 (cell) On 24.05.14 21:41, "Graham Charters" <[email protected]> wrote: >Hi Tim, > >The Subsystems specification does not prescribe an approach to update. >When we discussed this in the Expert Group it was concluded that there >were a number of different possible strategies (as your email points out) >and so > it would be premature to pick one. > >Version ranges on the Subsystem-Content entries enable different version >of a bundle to be deployed for the same application, thus allowing >'fixes' to be applied without having to create a new application >definition. The exact > approach to update is left to the implementor. Deployment manifests >allow versions to be locked down, or as you mention, it can be left to >the runtime to pick the exact versions. > >With OSGi applications on WebSphere Application Server (similar to >application Subsystems), we allow bundle updates in running applications >and preserve the configuration (only requiring net new config to be >supplied). An alternative > approach would be to do side-by-side deployment and migrate traffic >across to the new instance. > >Hope this clarifies things. > > >Regards, > >Graham. > > > >Graham Charters PhD CEng MBCS CITP >STSM, WebSphere OSGi Applications Lead Architect, Master Inventor >IBM United Kingdom Limited, MP 146, Hursley Park, Winchester, SO21 2JN, UK >Tel: (Ext) +44-1962-816527 (Int) 7-246527 (Fax) +44-1962-816527 >Internet: [email protected] > > > > >From: Tim Diekmann <[email protected]> >To: [email protected], EEG <[email protected]>, > >Date: 23/05/2014 22:21 >Subject: [eeg] Subsystems: hotfix workflow >Sent by: [email protected] >________________________________________ > > > >Hi, > >I am interested to hear what the proposed workflow looks like with >Subsystems to provide a hotfix/service-pack for an Application. > >Does it require an Application to be declared with an open range >[x.y,x.y+1) for all constituents and then allow dynamic resolution on >start? >Or is it simply a re-packaging of the Application with new constituents? > >In the ladder case, how does Subsystems handle the upgrade of the >application? Does it mean the existing version needs to be uninstalled >and a new version installed? If so, what happens to configurations of the >existing version? If they are removed, > how can they be migrated to be used by the new version? > >Or, in the end, is any of this out-of-scope and left to the implementer? > >Thanks, > > Tim. >_______________________________________________ >OSGi Enterprise Expert Group >[email protected] >https://mail.osgi.org/mailman/listinfo/eeg >All email submissions and replies to OSGi Alliance email addresses are >subject to the terms and conditions of the OSGi Alliance membership >agreement. > > >Unless stated otherwise above: >IBM United Kingdom Limited - Registered in England and Wales with number >741598. >Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU _______________________________________________ OSGi Enterprise Expert Group [email protected] https://mail.osgi.org/mailman/listinfo/eeg All email submissions and replies to OSGi Alliance email addresses are subject to the terms and conditions of the OSGi Alliance membership agreement. Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
