[
https://issues.apache.org/jira/browse/SSHD-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180539#comment-17180539
]
Matt Sicker commented on SSHD-1060:
-----------------------------------
If you used the lambda logger methods (log4j-api or slf4j-api 2.x), you can get
a more succinct version of {{if (logger.isDebugEnabled())
logger.debug("foo")}}. That would also allow for using markers in addition to
loggers to help categorize related log events that are sourced from different
loggers. Going further, you could even using log4j-audit or similar to keep an
audit trail of specific application events.
> Do not store logger level in fields
> -----------------------------------
>
> Key: SSHD-1060
> URL: https://issues.apache.org/jira/browse/SSHD-1060
> Project: MINA SSHD
> Issue Type: Improvement
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Priority: Major
> Fix For: 2.6.0
>
>
> The log levels can be changed at runtime externally, so the
> {{isDebugEnabled()}} or {{isTraceEnabled()}} should not be stored in fields.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org
