[
https://issues.apache.org/jira/browse/FELIX-6470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623999#comment-17623999
]
Carsten Ziegeler commented on FELIX-6470:
-----------------------------------------
Actually, the delivery to the managed service for the provided test case is
correct - the configuration gets created and deleted during the coordination,
therefore after the coordination is finished, the managed service is updated
with the latest state which is a non existing configuration.
However, the behaviour is not optimal,/correct when the configuration is not
deleted within the coordination. In this case the managed service is updated
three times - if more than two updates happen within a coordination this can
even lead to out of order delivery.
We should collapse the notification to a minimum to avoid churn
> ConfigAdmin/Coordinator handling not Spec-complient
> ---------------------------------------------------
>
> Key: FELIX-6470
> URL: https://issues.apache.org/jira/browse/FELIX-6470
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Affects Versions: configadmin-1.9.22
> Reporter: Stefan Bischof
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: configadmin-1.9.26
>
>
> The ConfigAdmin in combination with the Coordinator does not correctly
> deliver existing Configuration to later registered ManagedService.
> A Test could be found here.
> https://github.com/osgi/osgi/pull/343
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
