Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.9
-
None
-
None
Description
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.
Attachments
Issue Links
- is related to
-
CONFIGURATION-153 Use a strategy pattern for locating resources
- Closed