You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2013/05/31 07:13:20 UTC
[jira] [Resolved] (LOG4J2-249) Log4jContextListener: Support
property substitution in context-params
[ https://issues.apache.org/jira/browse/LOG4J2-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers resolved LOG4J2-249.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.0-beta7
Implemented in revision 1488095. Please verify and close.
> Log4jContextListener: Support property substitution in context-params
> ---------------------------------------------------------------------
>
> Key: LOG4J2-249
> URL: https://issues.apache.org/jira/browse/LOG4J2-249
> Project: Log4j 2
> Issue Type: Improvement
> Affects Versions: 2.0-beta5
> Reporter: Tim Tucker
> Priority: Minor
> Fix For: 2.0-beta7
>
>
> Similar to the property substitution options offered in log4j2.xml, it would be useful to allow for property substitution in the context-params for configuring Log4jContextListener.
> For example, we'd like to be able to do the following:
> <context-param>
> <param-name>log4jConfiguration</param-name>
> <param-value>${env:myVar}.log4j2.xml</param-value>
> </context-param>
> And have the value of myVar replaced at runtime.
> (in our case, we have integration / production systems that have 1 environment variable set that controls the behavior of multiple deployed applications, each of which have different config files for each environment)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org