[
https://issues.apache.org/jira/browse/SLING-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-5888:
-----------------------------------
Attachment: SLING-5888-v01.patch
Attached is a first patch for a new bundle (next to installer.core).
I would like to gather some feedback, especially on the following points:
# In other places {{hc}} is used instead of {{healthcheck}} for package names
and symbolic names. I do like the long version better, but the short version
would be more in line with the other health check bundles.
# The bundles check in this health check is known to fail in the commons case
where a system bundle has been provided in the repository to support a broader
range of Sling systems: It could either be that this system bundle was not part
of an older Sling version or was just updated to at least the shipped version
with a newer version of Sling. For all users running the application on top of
the newer Sling version the health check would fail, because in that case the
OSGi installer would ignore the bundle from the application (since it has
already been installed in the same or in a newer version on the system from
another location).
> 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).
> 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)
