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 2008/10/14 21:33:44 UTC

[jira] Commented: (CONFIGURATION-340) Allow configuration files to be stored in many locations

    [ https://issues.apache.org/jira/browse/CONFIGURATION-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639555#action_12639555 ] 

Oliver Heger commented on CONFIGURATION-340:
--------------------------------------------

CONFIGURATION-153 also contains some thoughts about extending the mechanism for loading configurations. Especially there is a link to a thread we had a long while ago about the concept of so-called "Locators".

Maybe you want to have a look at this discussion. It would be interesting to get another opinion!

> Allow configuration files to be stored in many locations
> --------------------------------------------------------
>
>                 Key: CONFIGURATION-340
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-340
>             Project: Commons Configuration
>          Issue Type: Improvement
>         Environment: All
>            Reporter: Ralph Goers
>
> AbstractFileConfiguration currently gets or stores files on the local file system or via http. Commons Configuration should be enhanced so that files can be stored or retrieved using almost any mechanism. For example, using Commons VFS or constructs like Maven's Wagon would allow files to be housed in a source control system, a CMS, a database or anything else one could dream up. This is important to me as I need to be able to store and retrieve my configuration files using WebDav (with CHECKIN and CHECKOUT). 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.