[
https://issues.apache.org/jira/browse/LOG4J2-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187446#comment-15187446
]
Matt Sicker commented on LOG4J2-1169:
-------------------------------------
I don't think the Configuration needs to be looked up from a LoggerContext. The
factory for this class already gets a Configuration which looks to be the same
one that is looked up again in {{parseSubstitution(LogEvent)}}.
> PatternLayout: Possible variable substitution in equals substitution parameter
> ------------------------------------------------------------------------------
>
> Key: LOG4J2-1169
> URL: https://issues.apache.org/jira/browse/LOG4J2-1169
> Project: Log4j 2
> Issue Type: Improvement
> Components: Pattern Converters
> Affects Versions: 2.4.1
> Reporter: Gerald Kritzinger
> Priority: Critical
> Attachments: LOG4J2-1169.patch
>
>
> Let the substitution parameter of the equals function also substitute
> variables.
> E.g.:
> {noformat}
> %equals{%marker}{}{%msg}
> {noformat}
> should print the message if the marker is empty, currently "%msg" is appended.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
