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 2018/04/30 08:05:00 UTC

[jira] [Closed] (FELIX-5778) Refactor factory configuration handling

     [ https://issues.apache.org/jira/browse/FELIX-5778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed FELIX-5778.
-----------------------------------

> Refactor factory configuration handling
> ---------------------------------------
>
>                 Key: FELIX-5778
>                 URL: https://issues.apache.org/jira/browse/FELIX-5778
>             Project: Felix
>          Issue Type: Improvement
>          Components: Configuration Admin
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: configadmin-1.9.0
>
>
> The current factory configuration handling is complicated and seems to missing proper synchronization. There is a Factory object holding the set of configurations belonging to a single factory configuration. However this is maintained/synchronized at a different place than the configurations in the persistence manager. This could lead to subtle race conditions.
>  
> I think we can get away with doing all the caching in the persistence manager (proxy) and avoid the need of additional synchronization. In addition, there should be no need to store the list of configurations belonging to a factory configuration into the persistence



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)