[FELIX-658] Extend deployment admin to optionally support not stopping the world on updates.

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: Deployment Admin
• Assignee: Unassigned
• Reporter: Marcel Offermans
• Created: 04/Aug/08 12:10
• Updated: 01/Apr/14 12:48
• Resolved: 04/Aug/08 13:23

Description

Deployment Admin supports the atomic installation, update and removal of a group of bundles called a package. Once installed, you can create fix packages to upgrade from one version to the next. Often, those updates only contain a subset of the bundles. However (and this is very un-OSGi-like) the spec dictates that even if you update only one bundle in a package, you have to first stop them all, then do the update, and finally start them all again. I would like to have a switch that allows you to change this behavior to only update what is actually changed.

Background: To maintain the software and updates to a gateway, we often define a gateway to contain one deployment package containing all bundles, because that's the only way to truly create atomic updates (once you start having more deployment packages, you run the risk of wanting to update things in more than one package, and then run into the issue that there is no overarching mechanism to do those updates in one transaction).