[
https://issues.apache.org/jira/browse/LOG4J2-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135079#comment-13135079
]
Ralph Goers commented on LOG4J2-28:
-----------------------------------
The experimental version of Log4j 2.0 borrows from the StrSubstitutor and
StrLookup in Commons Lang and Interpolator in Commons Configuration. The
configuration currently supports resolving properties from the MDC, System
Properties, inline in the configuration, Environment Variables and data in
StructuredDataMessages. Variables of the form ${xxx:name} will be resolved by
the Configuration directly while variables of the form $${xxx:name} will be
passed as ${xxx:name} to allow the underlying component to resolve them at
execution time.
> Increased support for properties
> --------------------------------
>
> Key: LOG4J2-28
> URL: https://issues.apache.org/jira/browse/LOG4J2-28
> Project: Log4j 2
> Issue Type: Wish
> Components: API
> Reporter: Curt Arnold
>
> On Dec 3, 2008, at 10:22 PM, Scott Deboy wrote on log4j-dev:
> ...
> Whatever we do moving forward, I'd like to see increased support for
> properties. MDC and NDC are useful, but something that isn't thread specific
> would be useful (one reason why property rewrite policy/rewriteappender were
> created was to get around this limitation).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
