You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Oliver Heger (JIRA)" <ji...@apache.org> on 2014/05/24 15:48:01 UTC
[jira] [Resolved] (CONFIGURATION-559) Support setting default
values for configurations
[ https://issues.apache.org/jira/browse/CONFIGURATION-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Heger resolved CONFIGURATION-559.
----------------------------------------
Resolution: Fixed
This feature has been implemented and also documented in the user's guide.
> Support setting default values for configurations
> -------------------------------------------------
>
> Key: CONFIGURATION-559
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-559
> Project: Commons Configuration
> Issue Type: New Feature
> Affects Versions: 1.9
> Reporter: Oliver Heger
> Fix For: 2.0
>
>
> In version 1.x it was possible to set a few default values for the properties of configuration instances (e.g. the list delimiter or the expression engine for XML configurations). These settings were used if they were not overridden for a specific configuration instance. This mechanism was mainly based on static fields which is unflexible and thread-hostile.
> In the new design, configuration builders are used to create configuration objects. Parameter objects can be passed to the builder allowing a fine-grained configuration of the instances to be created. Because there are many settings it would be helpful if there was a way to define certain default values. An application creating multiple configuration instances with the same settings could define the used defaults once and then reuse them.
> Default settings should be possible for all parameters object supported by the different builder implementations. No static fields should be used to avoid the drawbacks of the current design.
--
This message was sent by Atlassian JIRA
(v6.2#6252)