[ https://issues.apache.org/jira/browse/LOG4J2-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321700#comment-15321700 ]
Gary Gregory commented on LOG4J2-1418: -------------------------------------- Sure, but we should also audit our use of {{getMessageFactory()}} and replace it with {{getMessageFactory2()}} where appropriate. The previous example of internal logging might be an edge case but we should still eat our own dog food. > Provide MessageFactory2 to custom Logger implementations > -------------------------------------------------------- > > Key: LOG4J2-1418 > URL: https://issues.apache.org/jira/browse/LOG4J2-1418 > Project: Log4j 2 > Issue Type: Improvement > Components: API > Affects Versions: 2.6 > Reporter: Mikael Ståldal > > It would be useful for a custom Logger implementation to be able to get hold > of a {{MessageFactory2}} (and not just a {{MessageFactory}}), in order to > efficiently process {{CharSequence}} etc. > {{Logger.getMessageFactory()}} return {{MessageFactory}}, even though the > sole implementation in {{AbstractLogger}} do have a {{MessageFactory2}} > available. -- 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