[
https://issues.apache.org/jira/browse/DIRMINA-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514839
]
Mark Webb commented on DIRMINA-376:
-----------------------------------
I am going to check in this code, and use the
Collections.synchronizedMap(Map<V,K>) method for creating the java.util.Map
that holds the settings. I will open a new JIRA entry for adding a
CopyOnWriteMap and CopyOnReadMap. This way the new LoggingFilter can begin the
review process by other developers.
> 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
> 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.
