You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@felix.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2022/10/25 19:35:00 UTC

[jira] [Commented] (FELIX-6470) ConfigAdmin/Coordinator handling not optimal

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

Carsten Ziegeler commented on FELIX-6470:
-----------------------------------------

Potential fix at https://github.com/apache/felix-dev/commit/3a715de8f163cd967e412db857ac2236cd891fd2

which collapses several updates to a single update, removes notifications for a config that gets created and deleted within a coordination and reduces the calls to the managed service (factory) to one

> ConfigAdmin/Coordinator handling not optimal
> --------------------------------------------
>
>                 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)