sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Bosschaert (JIRA)" <>
Subject [jira] [Commented] (SLING-7496) Factory config deleted with ConfigAdmin immediately after creation
Date Mon, 19 Feb 2018 16:20:00 GMT


David Bosschaert commented on SLING-7496:

Hi [~cziegele] I guess the test case was incorrect in that is wasn't waiting for the system
to reach the initial INSTALLED state for the configurations. I added an extra check to the
test cases, and reverted the state to IGNORED where it had this state before.

> Factory config deleted with ConfigAdmin immediately after creation
> ------------------------------------------------------------------
>                 Key: SLING-7496
>                 URL:
>             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

View raw message