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 2016/12/28 12:52:58 UTC
[jira] [Resolved] (FELIX-5468) Refactor persistence handling
[ https://issues.apache.org/jira/browse/FELIX-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved FELIX-5468.
-------------------------------------
Resolution: Fixed
Rev 1776276
Refactored persistence handling into two proxies: caching and non caching.
There is still complicated code in ConfigurationManager but I'm not going to touch this for now
> Refactor persistence handling
> -----------------------------
>
> Key: FELIX-5468
> URL: https://issues.apache.org/jira/browse/FELIX-5468
> Project: Felix
> Issue Type: Improvement
> Components: Configuration Admin
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: configadmin-1.9.0
>
>
> The handling of persistence managers has grown over time and has now a rather entangled implementation checking in various places if the underlying persistence manager is caching or not.
> In addition read/write locking is done on a persistence manager level but not across all available persistence managers.
> I think if we move the whole persistence manager handling code into a separate component, the code gets cleaner and easier to test
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)