[
https://issues.apache.org/jira/browse/LOG4J2-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225930#comment-15225930
]
Remko Popma commented on LOG4J2-1353:
-------------------------------------
So to clarify, the requirement is that both of these usages:
{code}
logger.debug("message without placeholders", "param1", "param2", "param3");
logger.debug("message with placeholders {} {} {}", "param1", "param2",
"param3");
{code}
...should produce the same result:
{code}
DEBUG ... message without placeholders param1 param2 param3
DEBUG ... message with placeholders param1 param2 param3
{code}
> Logger 'Object... params' arguments should always be appended even if {} is
> missing
> -----------------------------------------------------------------------------------
>
> Key: LOG4J2-1353
> URL: https://issues.apache.org/jira/browse/LOG4J2-1353
> Project: Log4j 2
> Issue Type: New Feature
> Components: API
> Affects Versions: 2.5
> Reporter: Alex Berg
> Priority: Minor
>
> The Logger.warn/info/trace etc. has methods that take ... object list. It
> maps into message where {} is given. If there are fewer {} than arguments in
> list, it ignores argument. Who would ever desire to have an argument ignored?
> That is to me clearly a bug in the design, but of cause I may be missing
> something.
> I suggest to always append the unmatched extra arguments and separate them by
> a space or a comma. I'm not sure if the last argument is logged as an
> exception if it is an exception, in that case the solution should gracefully
> handle that.
> A super nice feature would be if it was possible to configure the append of
> the unmatched arguments, but I think that is more work than it is worth.
> see http://logging.apache.org/log4j/2.x/log4j-api/apidocs/index.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
