[
https://issues.apache.org/jira/browse/SLING-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665419#action_12665419
]
Felix Meschberger commented on SLING-713:
-----------------------------------------
As part of Rev. 735999 the launchpad application setup has been completely
refactored. All classes and active components are now contained in the
launchpad/base module only. The other launchpad modules -- app, webapp,
testing, jcrapp -- only recombine different parts of the base such that the
resulting standalone application or web application becomes useful.
See also http://cwiki.apache.org/SLING/the-sling-launchpad.html for more
information.
> Allow the Framework to restart
> ------------------------------
>
> Key: SLING-713
> URL: https://issues.apache.org/jira/browse/SLING-713
> Project: Sling
> Issue Type: New Feature
> Components: Launchpad Launcher
> Affects Versions: Launchpad Base 2.0.2
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
>
> Certain operations may cause the OSGi framework to restart, such as calling
> Bundle.update on the system bundle or calling Bundle.stop on the system
> bundle (this should maybe even cause the application to terminate) or
> removing a framework extension bundle.
> The Sling launcher is in control of the Felix framework launch and therefore
> can easily cope with framework restart requests. In addition OSGi will bring
> more information on why the framework is terminating as to decide whether the
> launcher should relaunch the framework or simply terminate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
