You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Trustin Lee (JIRA)" <ji...@apache.org> on 2007/09/30 17:59:50 UTC
[jira] Closed: (DIRMINA-376) Fine-grained logging control in
LoggingFilter
[ https://issues.apache.org/jira/browse/DIRMINA-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Trustin Lee closed DIRMINA-376.
-------------------------------
Resolution: Fixed
The new filter looks great to me. Great job Mark! It's time to close. :)
> Fine-grained logging control in LoggingFilter
> ---------------------------------------------
>
> Key: DIRMINA-376
> URL: https://issues.apache.org/jira/browse/DIRMINA-376
> Project: MINA
> Issue Type: New Feature
> Components: Filter
> Reporter: Trustin Lee
> Assignee: Mark Webb
> Priority: Minor
> Fix For: 2.0.0-M1
>
>
> LoggingFilter of MINA 1.0 has limited usability because there's no way to disable certain log messages. For example, you can't:
> * disable logging for certain event type (e.g. exceptionCaught, which is often logged again in IoHandler.exceptionCaught()).
> * log only certain type of received messages
> Category filtering feature provided by logging frameworks will solve this problem somewhat, but it's very coarse-grained and won't work as expected because LoggingFilter gets the logger instance using the IoHandler implementation class and therefore affect logging messages in an IoHandler implementation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.