[
https://issues.apache.org/jira/browse/LOG4J2-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457958#comment-13457958
]
Ralph Goers commented on LOG4J2-86:
-----------------------------------
Thanks. If the doc says the level is error and it is actually debug then I will
have to fix one of those. SLF4J's XLogger has these same methods and I'd like
it to behave the same as those.
Please keep making suggestions and, if you're feeling ambitious, attach patches.
> 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
