felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-5778) Refactor factory configuration handling
Date Wed, 24 Jan 2018 16:31:00 GMT

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

Carsten Ziegeler resolved FELIX-5778.
    Resolution: Fixed

I managed to get rid of the Factory class and it's caching in the ConfigurationManager. In
addition, there is no need to persist the relation of factory configurations anymore. The
persistence manager proxy is building up this information while reading configurations and
all the caching is now done at this single place

> 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

View raw message