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/04/01 05:53:15 UTC
[jira] [Resolved] (LOG4J2-157) Provide access to config properties
in LoggerConfig
[ https://issues.apache.org/jira/browse/LOG4J2-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers resolved LOG4J2-157.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.0-beta5
Assignee: Ralph Goers
Patch applied in revision 1463078. Please verify and close.
> Provide access to config properties in LoggerConfig
> ---------------------------------------------------
>
> Key: LOG4J2-157
> URL: https://issues.apache.org/jira/browse/LOG4J2-157
> Project: Log4j 2
> Issue Type: New Feature
> Components: Configurators
> Affects Versions: 2.0-beta4
> Reporter: Remko Popma
> Assignee: Ralph Goers
> Fix For: 2.0-beta5
>
> Attachments: LOG4J2-157-patch.txt
>
>
> Custom Loggers that want to support configuration properties when creating custom LogEvent objects currently have no easy way to access these configuration Property objects.
> The configuration Property map in LoggerConfig is private. Please provide an accessor method that returns a (read-only) view of this Property map.
> proposal: add below method to org.apache.logging.log4j.core.config.LoggerConfig:
> /**
> * Returns an unmodifiable map with the configuration properties, or
> * {@code null} if this {@code LoggerConfig} does not have any configuration
> * properties.
> * <p>
> * For each {@code Property} key in the map, the value is {@code true} if
> * the property value has a variable that needs to be substituted.
> *
> * @return an unmodifiable map with the configuration properties, or
> * {@code null}
> * @see Configuration#getSubst()
> * @see StrSubstitutor
> */
> public Map<Property, Boolean> getProperties() {
> return properties == null ? null :
> Collections.unmodifiableMap(properties);
> }
--
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