You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2011/08/29 17:12:38 UTC

[jira] [Closed] (FELIX-3094) [Main] Launcher should attempt to restart framework if the system bundle was updated

     [ https://issues.apache.org/jira/browse/FELIX-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard S. Hall closed FELIX-3094.
----------------------------------

    Resolution: Fixed

Fixed in trunk.

> [Main] Launcher should attempt to restart framework if the system bundle was updated
> ------------------------------------------------------------------------------------
>
>                 Key: FELIX-3094
>                 URL: https://issues.apache.org/jira/browse/FELIX-3094
>             Project: Felix
>          Issue Type: Improvement
>          Components: Main
>    Affects Versions: framework-3.2.2
>            Reporter: Richard S. Hall
>            Assignee: Richard S. Hall
>            Priority: Minor
>             Fix For: framework-4.0.0
>
>
> The launcher starts the framework then calls Framework.waitForStop(), which returns a FrameworkEvent with a type value to indicate why the framework was stopped. If the system bundle was updated/refreshed, then according to the spec the framework should be restarted. Although technically, this should probably restart the JVM process, we can support a weak restart by simply having the launcher restart the framework any time waitForStop() exits with FrameworkEvent.STOPPED_UPDATE.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira