commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CONFIGURATION-536) Rework file configurations
Date Thu, 04 Apr 2013 19:44:15 GMT

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

Oliver Heger resolved CONFIGURATION-536.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0

The handling of file-based configurations has been redesigned.

The central class for I/O operations on configuration objects is now {{FileHandler}}. It replaces
the base classes {{AbstractFileConfiguration}} and {{AbstractHierarchicalFileConfiguration}}.
Configuration classes supporting files need to implement the {{FileBased}} interface.
                
> Rework file configurations
> --------------------------
>
>                 Key: CONFIGURATION-536
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-536
>             Project: Commons Configuration
>          Issue Type: Improvement
>    Affects Versions: 1.9
>            Reporter: Oliver Heger
>             Fix For: 2.0
>
>
> The inheritence hierarchy of file configurations is currently very complex. There is
duplicated code between plain file configurations and hierarchical ones. Also, many methods
of the {{Configuration}} interface have to be overloaded to implement functionality related
to file configurations.
> The goal of this ticket is to extract code related to loading and saving of file configurations
to a central place. Also, a replacement for the auto save functionality has to be implemented
(e.g. a special event listener). After that, the classes {{AbstractFileConfiguration}} and
{{AbstractHierarchicalFileConfiguration}} can be removed.
> Note: Reloading functionality is now handled by configuration builders.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message