[
https://issues.apache.org/jira/browse/SLING-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782360#action_12782360
]
Felix Meschberger commented on SLING-1200:
------------------------------------------
Modified the startup behaviour of the launchpad:
* The BootstrapInstaller installs a framework listener which upon the
framework STARTED event decides whether to
go into the initially desired start level or to restart the framework. This
depends on whether during startup a framework
extension bundle has been updated or not.
* The Sling class launching the framework ensures the OSGi framework
beginning start level property is set to 1
to not fully start the framework automatically but give the framework
listener installed by the BootstrapInstaller give
the option to continue startup or to restart.
Implemented in Rev. 884022
> Restart framework if BootstrapInstaller updates a framework extension
> fragment bundle
> -------------------------------------------------------------------------------------
>
> Key: SLING-1200
> URL: https://issues.apache.org/jira/browse/SLING-1200
> Project: Sling
> Issue Type: Improvement
> Components: Launchpad
> Affects Versions: Launchpad Base 2.0.4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: Launchpad Base 2.0.6
>
>
> The spec mandates that updating a framework extension (fragment) bundle
> requires a framework restart for the updated framework extension to become
> active.
> If the Sling Launchpad BootstrappInstaller updates such a bundle it would be
> good to automatically restart the framework after such an update to actually
> activate this update.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
