[
https://issues.apache.org/jira/browse/SLING-7876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated SLING-7876:
------------------------------
Description:
Since OSGi R7 the framework will return a new exit code on stop when it is
being shutdown because of an extension bundle refresh. Up until Felix 6 the
launchpad base handled this case together with an update call on the framework
itself (as Felix internally went through the same update method in both cases)
- however, due to the new R7 way of doing things this has stopped working and
the framework will not be restarted if the stop was because of a refresh of an
extension bundle.
We need to trap the refresh exit code and restart the framework in that case.
was:
Sind OSGi R7 the framework will return a new exit code on stop when it is being
shutdown because of an extension bundle refresh. Up until Felix 6 the launchpad
base handled this case together with an update call on the framework itself (as
Felix internally went through the same update method in both cases) - however,
due to the new R7 way of doing things this has stopped working and the
framework will not be restarted if the stop was because of a refresh.
We need to trap the refresh exit code and restart the framework in that case.
> Launchpad Base needs to take framework restarts due to extension bundle
> refresh into account.
> ---------------------------------------------------------------------------------------------
>
> Key: SLING-7876
> URL: https://issues.apache.org/jira/browse/SLING-7876
> Project: Sling
> Issue Type: Bug
> Components: Launchpad
> Affects Versions: Launchpad Base 2.6.30
> Reporter: Karl Pauls
> Assignee: Karl Pauls
> Priority: Major
> Fix For: Launchpad Base 2.6.32
>
>
> Since OSGi R7 the framework will return a new exit code on stop when it is
> being shutdown because of an extension bundle refresh. Up until Felix 6 the
> launchpad base handled this case together with an update call on the
> framework itself (as Felix internally went through the same update method in
> both cases) - however, due to the new R7 way of doing things this has stopped
> working and the framework will not be restarted if the stop was because of a
> refresh of an extension bundle.
> We need to trap the refresh exit code and restart the framework in that case.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
