[
https://issues.apache.org/jira/browse/SLING-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-5888:
-----------------------------------
Description:
We faced an issue in the past that configurations (or bundles) being deployed
in the repository are not effective (i.e. not installed in Apache Felix).
The reason for that is that the OSGi configuration was either manually modified
in the Web Console (and therefore takes precedence over the version of the
configuration being deployed in the repository) or in case of bundles, that the
same bundle has already been deployed in that or a newer version (manually or
through some other path in the repository/filesystem).
Both states may lead to issues at run time, so it would be good to have an
automated check for it.
was:
We faced an issue in the past that configurations (or bundles) being deployed
in the repository are not effective (i.e. not installed in Apache Felix).
The reason for that is that the OSGi configuration was either manually modified
in the Web Console (and therefore takes precedence over the version of the
configuration being deployed in the repository) or in case of bundles, that the
same bundle has already been deployed in that or a newer version (manually or
through some other path in the repository).
Both states may lead to issues at run time, so it would be good to have an
automated check for it.
> Health Check for detecting not-installed configurations/bundles from the OSGi
> installer
> ---------------------------------------------------------------------------------------
>
> Key: SLING-5888
> URL: https://issues.apache.org/jira/browse/SLING-5888
> Project: Sling
> Issue Type: Improvement
> Components: Health Check, Installer
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Attachments: SLING-5888-v01.patch
>
>
> We faced an issue in the past that configurations (or bundles) being deployed
> in the repository are not effective (i.e. not installed in Apache Felix).
> The reason for that is that the OSGi configuration was either manually
> modified in the Web Console (and therefore takes precedence over the version
> of the configuration being deployed in the repository) or in case of bundles,
> that the same bundle has already been deployed in that or a newer version
> (manually or through some other path in the repository/filesystem).
> Both states may lead to issues at run time, so it would be good to have an
> automated check for it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
