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] [Commented] (FELIX-5468) Refactor persistence handling
Date Fri, 26 May 2017 05:16:04 GMT

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

Carsten Ziegeler commented on FELIX-5468:

[~topolik] Thanks for reporting. The changes of this issue are currently only for master (version
1.9.0), the configadmin directory contains version 1.8.x where we didn't apply the changes.
If there is a need of a back port to that branch to release a fix for 1.8.x, please let us

> 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

View raw message