[LOG4J2-1418] Provide MessageFactory2 to custom Logger implementations

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6, 2.6.1
• Fix Version/s: 2.6.2
• Component/s: API
• Epic Link: GC-free
• Assignee: Mikael Ståldal
• Reporter: Mikael Ståldal
• Created: 08/Jun/16 16:11
• Updated: 23/Oct/20 19:55
• Resolved: 18/Sep/16 10:39

Description

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.