sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-7496) Factory config deleted with ConfigAdmin immediately after creation
Date Fri, 16 Feb 2018 16:23:00 GMT

    [ https://issues.apache.org/jira/browse/SLING-7496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367544#comment-16367544
] 

ASF GitHub Bot commented on SLING-7496:
---------------------------------------

bosschaert opened a new pull request #1: SLING-7496 Factory configurations get deleted on
update()
URL: https://github.com/apache/sling-org-apache-sling-installer-factory-configuration/pull/1
 
 
   The factory prefix was prepended twice which caused the installer to
   think that the original configuration being updated was gone, which
   triggered a callback to Configuration.delete();

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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
>            Reporter: David Bosschaert
>            Priority: Major
>             Fix For: Installer Configuration Factory 1.1.2
>
>
> 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)

Mime
View raw message