You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2010/05/15 08:35:41 UTC
[jira] Commented: (LOG4J2-24) Have an API method that does a deeper
evaluation than Logger.isDebugEnabled() of whether logging will occur
[ https://issues.apache.org/jira/browse/LOG4J2-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12867809#action_12867809 ]
Ralph Goers commented on LOG4J2-24:
-----------------------------------
If I understand the issue correctly, this can be addressed by using Filters as implemented in my experimental branch. Filters can be global, on a logger or on an appender.
> Have an API method that does a deeper evaluation than Logger.isDebugEnabled() of whether logging will occur
> -----------------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-24
> URL: https://issues.apache.org/jira/browse/LOG4J2-24
> Project: Log4j 2
> Issue Type: Wish
> Reporter: Curt Arnold
>
> See https://issues.apache.org/bugzilla/show_bug.cgi?id=45368
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org