[SLING-5887] OSGi Installer: configuration factory instances and regular configuration instances differ in terms of overwrite behaviour

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: Installer Core 3.6.4, JCR Installer 3.1.16
• Component/s: Installer
• Assignee: Unassigned
• Reporter: Konrad Windszus
• Created: 22/Jul/16 08:19
• Updated: 04/Sep/19 08:04

Description

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.

Issue Links

• relates to: SLING-7736 OSGi Installer: Update OSGi installer's resource state in case of configuration/bundle updates outside of the OSGi Installer when JCR Installer Writeback is disabled
• relates to: SLING-6313 Sling installer can duplicate factory configurations if an invalid RegisteredResourceList.ser is found