[
https://issues.apache.org/jira/browse/LOG4J2-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503605#comment-17503605
]
Carter Kozak commented on LOG4J2-3345:
--------------------------------------
The System.Logger API that this implements requires MessageFormat formatting,
the api is not aware of curly brace placeholders without indices:
[https://docs.oracle.com/javase/9/docs/api/java/lang/System.Logger.html#log-java.lang.System.Logger.Level-java.lang.String-java.lang.Object...-]
> format - the string message format in
> [{{MessageFormat}}|https://docs.oracle.com/javase/9/docs/api/java/text/MessageFormat.html]
> format
Libraries which consume this API cannot make assumptions about what types of
formatting will be supported by the underlying logging framework. That would be
reasonable if they used log4j-api or slf4j loggers which explicitly support
curly brace placeholders, but not System.Logger.
> log4j-jpl must handle parameters as MessageFormat args
> ------------------------------------------------------
>
> Key: LOG4J2-3345
> URL: https://issues.apache.org/jira/browse/LOG4J2-3345
> Project: Log4j 2
> Issue Type: Bug
> Components: JPL Adapter
> Affects Versions: 2.17.1
> Reporter: Carter Kozak
> Assignee: Carter Kozak
> Priority: Major
> Fix For: 2.17.2
>
>
> Currently message parameters use the configured default messagefactory, which
> provides no guarantees around the format used, however JPL API requires
> MessageFormat style formatting.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
