[
https://issues.apache.org/jira/browse/SLING-7496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16369105#comment-16369105
]
David Bosschaert commented on SLING-7496:
-----------------------------------------
Hi [~cziegeler] I could be wrong but this is I think the thing that we aimed to
fix in this issue in the first place. Originally, because of a mismatch in pids
(that had a double factory pid prefixed) when a configuration was created, it
was deleted immediately, causing the configuration resource to be assigned the
IGNORED state. Since that delete is now not happening any more at the initial
state, the resource stays in the INSTALLED state which seems correct...
Again, I could be wrong, but this is how I understand it :)
> Factory config deleted with ConfigAdmin immediately after creation
> ------------------------------------------------------------------
>
> Key: SLING-7496
> URL: https://issues.apache.org/jira/browse/SLING-7496
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Affects Versions: Installer Configuration Factory 1.1.2
> Reporter: David Bosschaert
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: Installer Configuration Factory 1.2.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
