Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
Installer Configuration Factory 1.1.2
-
None
Description
In some cases when a factory configuration is created using the OSGi ConfigAdmin API, the configuration gets a call to delete() immediately when update() on the configuration is called.
The issue comes down to the fact that the factory prefix is prepended twice to the configuration at some point in the installer, which is then assigned to the resource entityId. This mismatch causes the initial configuration to receive a delete callback as the system thinks it's no longer there.