Currently there are many ways to specify the location for a file-based configuration: as a URL, as a File, a file name, a base path... It was a major effort to keep the several get and set methods for these properties in sync.

With the new implementation based on the FileSystem class (which I have not yet studied in detail I have to confess) I wonder whether there is a better approach for the configuration2 branch. Would it be possible to simplify the interface for file-based configurations, e.g. by introducing a generic Locator class?

Another remark about the DefaultFileSystem class: Currently the functionality for locating files seems to be smeared between DefaultFileSystem and ConfigurationUtils. Would it be better to refactor it into a central location?

Oliver

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to