[
https://issues.apache.org/jira/browse/SLING-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16524950#comment-16524950
]
Konrad Windszus commented on SLING-5745:
----------------------------------------
Actually, it is currently possible to manually overwrite the configuration or
the bundle (with the Web Console) without the OSGi Installer noticing it
(SLING-7736). In that case it would be helpful to just reinstall the
configuration/bundles from the OSGi Installer.
> Provide a button to clear all registered entities and reinstall those
> ---------------------------------------------------------------------
>
> Key: SLING-5745
> URL: https://issues.apache.org/jira/browse/SLING-5745
> Project: Sling
> Issue Type: Improvement
> Components: Installer
> Affects Versions: Installer Console 1.0.2
> Reporter: Konrad Windszus
> Priority: Major
>
> Currently the web console at {{/system/console/osgi-installer}} exposes the
> history/state of the OSGi installer. In case the state is not reflecting
> reality for some reason, there should be a possibility to remove that history
> and restart the according bundles with a button inside that console.
> The actions which should be triggered under the hood should be
> # remove the data file {{RegisteredResourceList.ser}}
> # restart the bundle {{org.apache.sling.installer.core}}
> That should lead to every provider being asked about all entities which are
> then processed again so you end up with state again where the most
> prioritized entites are deployed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
