[
https://issues.apache.org/jira/browse/SLING-5887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922264#comment-16922264
]
Carsten Ziegeler commented on SLING-5887:
-----------------------------------------
[~kwin] Could you please check whether this still is an issue with latest
versions?
> OSGi Installer: configuration factory instances and regular configuration
> instances differ in terms of overwrite behaviour
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-5887
> URL: https://issues.apache.org/jira/browse/SLING-5887
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Affects Versions: Installer Core 3.6.4, JCR Installer 3.1.16
> Reporter: Konrad Windszus
> Priority: Major
>
> In case an OSGi configuration contributed through the JCR Installer is
> overwritten manually in the Felix Web Console, this new version takes
> precedence over the version in the repository. Even if the configuration in
> the repository is modified afterwards (i.e. the EventListener is being
> triggered) the manually overwritten configuration will not replaced with the
> version from the repository. Only explicitly deleting the manually
> overwritten configuration will lead to the repository version of it becoming
> active again.
> In contrast for OSGi configuration factories, every manually overwritten
> instance is automatically reverted to the repository version, in case the
> according configuration in the repository is updated.
> So it seems that the OSGi installer in that case does not detect, that this
> configuration instance was deliberately overwritten by the user.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
