You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by cz...@apache.org on 2015/03/10 12:33:30 UTC

svn commit: r1665483 - /sling/site/trunk/content/documentation/bundles/osgi-installer.mdtext

Author: cziegeler
Date: Tue Mar 10 11:33:30 2015
New Revision: 1665483

URL: http://svn.apache.org/r1665483
Log:
Document SLING-3749 - intelligent start level handling

Modified:
    sling/site/trunk/content/documentation/bundles/osgi-installer.mdtext

Modified: sling/site/trunk/content/documentation/bundles/osgi-installer.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/osgi-installer.mdtext?rev=1665483&r1=1665482&r2=1665483&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/osgi-installer.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/osgi-installer.mdtext Tue Mar 10 11:33:30 2015
@@ -47,6 +47,19 @@ The OSGi installer asumes that a symboli
 
 During development, SNAPSHOT versions should be used, like 1.0.0-SNAPSHOT (using the Maven convention). If a bundle with a snapshot version is changed, it gets updated by the OSGI installer.
 
+## Start Level Handling
+
+The OSGi installer supports handling of start levels for bundles. If the provided bundle artifacts contain a start level information the bundle is installed with that start level, otherwise the default start level is used.
+Therefore, for initial provisioning to make use of start levels, the OSGi installer and the corresponding provider (see below) should run at a very low start level, probably at 1. This ensure that the bundles with a start level are started with respect to the start level.
+
+When an update of bundles is performed through the installer, by default the installer stays in the current start level and updates the bundles. However, if bundles at low start levels are affected, this might result in a lot of churn going on. Therefore, the OSGi installer can be configured to use a more intelligent start level handling:
+
+* If the framework property "sling.installer.switchstartlevel" is set to "true" and
+* there is no asynchronous install task in the list of tasks to perform, then
+* the start level is set to (the lowest level of the bundles to be updated - 1) - if the start level is lower than the level of the installer itself, the start level of the installer is used.
+* the bundles are updated/installed
+* the start level is increased to the previous level
+
 ## Plugins
 
 ### Factories