You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2018/07/03 16:16:00 UTC

[jira] [Commented] (SLING-5745) Provide a button to clear all registered entities and reinstall those

    [ https://issues.apache.org/jira/browse/SLING-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16531616#comment-16531616 ] 

Konrad Windszus commented on SLING-5745:
----------------------------------------

This workaround is no longer recommended, because you no longer get the correct state in the OSGi Installer, because bundles which are already installed in the same version are just marked as "IGNORED" instead of "INSTALLED" (https://github.com/apache/sling-org-apache-sling-installer-core/blob/1561f5e626bab4859b4c060ef1bec06026018f18/src/main/java/org/apache/sling/installer/core/impl/tasks/BundleTaskCreator.java#L280) because they are already deployed in Felix in the same version.

> 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)