You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Oliver Heger (JIRA)" <ji...@apache.org> on 2007/01/27 19:38:49 UTC

[jira] Updated: (CONFIGURATION-221) Allow system properties in config.xml

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

Oliver Heger updated CONFIGURATION-221:
---------------------------------------

    Fix Version/s:     (was: Nightly Builds)
                   1.3

> Allow system properties in config.xml
> -------------------------------------
>
>                 Key: CONFIGURATION-221
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-221
>             Project: Commons Configuration
>          Issue Type: Improvement
>    Affects Versions: 1.2
>         Environment: All
>            Reporter: Rainer Jung
>         Assigned To: Oliver Heger
>             Fix For: 1.3
>
>         Attachments: commons-configuration_1_2_patch.txt
>
>
> The attached patch allows system properties in the filename attributes of a config.xml file used in the factory.
> The patch is very simple, since commons-digester parses the file and has a built in capability to do the property substitution.
> The dependency of commons-configuration to commons-digester goes up from version 1.5 to 1.6. The most recent version 1.7 of commons-digester is not necessary.
> The patch can easily be ported to 1.3 and trunk.
> Use case: often the config.xml files are contained in a distribution unit like a war file, that should not be manipulated after packaging. The path names in config.xml need some way of making them externally variable so that the packaging unit can be adoped to a special environment without repackaging. By allowing system properties in the file names, this can be done easily.
> The implementation is simple, short and low risk.
> It would be nice, if you considered the patch for inclusion in the next release.

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


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