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 2013/09/29 19:35:23 UTC

[jira] [Resolved] (CONFIGURATION-553) Support custom search strategies for configuration files

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

Oliver Heger resolved CONFIGURATION-553.
----------------------------------------

    Resolution: Fixed

Major changes have been applied to the code for accessing configuration files. Especially, the hard-code algorithm to resolve configuration files used in the past was broken up into a set of {{FileLocationStrategy}} implementations. Users can create their own custom location strategy using either already provided building blocks or creating custom implementations.

> Support custom search strategies for configuration files
> --------------------------------------------------------
>
>                 Key: CONFIGURATION-553
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-553
>             Project: Commons Configuration
>          Issue Type: Improvement
>    Affects Versions: 1.9
>            Reporter: Oliver Heger
>             Fix For: 2.0
>
>
> Via the {{FileSystem}} class it is already possible to influence locating and loading of configuration files. However, the API is quite complex, and it is not obvious which methods to override.
> It would be easier to have a specialized interface for a locator strategy. This would make the implementation of custom search strategies straight-forward. A default implementation of this interface can be provided which implements the currently used search algorithm (which is currently hard-coded in {{ConfigurationUtils}}).
> In general, there is room for improvements in the file system implementations. For instance, functionality seems to be partly implemented in {{ConfigurationUtils}} and partly in {{DefaultFileSystem}}. I would like to remove the code related to the localization of configuration files from {{ConfigurationUtils}} and create a specialized utility class in the {{io}} package.



--
This message was sent by Atlassian JIRA
(v6.1#6144)