[
https://issues.apache.org/jira/browse/LOG4J2-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457913#comment-13457913
]
Ivan Anev commented on LOG4J2-86:
---------------------------------
In general it's a strong argument against. Especially if this was the log4j 1.2
it would be unthinkable to make such a change. On the other hand log4j 2.0 is
still in alpha and you can think of improving the API a bit. This type of
logging seems to be the most common error logging we have in our project, so I
would still suggest introducing those methods as this makes the code more
intuitive (when logging exceptions).
> Provide a logging methods with only a Throwable object as parameters
> --------------------------------------------------------------------
>
> Key: LOG4J2-86
> URL: https://issues.apache.org/jira/browse/LOG4J2-86
> Project: Log4j 2
> Issue Type: New Feature
> Components: API
> Reporter: Ivan Anev
> Fix For: 2.0-beta1
>
>
> Provide logging methods with only a Throwable object as a single parameter:
> info(Throwable e)
> error(Throwable e)
> ...
> The throwable objects contain a message themself and a stacktrace. So most of
> the times its pointless to log additional message. So in order to log them
> now you have to log an empty message and the throwable object:
> logger.error("", e);
> Which is obviously ugly and pointless when there is no reason not to have
> method like:
> logger.error(e);
> that should log both the message and the stacktrace.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
