[
https://issues.apache.org/jira/browse/DIRMINA-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513126
]
Mark Webb commented on DIRMINA-313:
-----------------------------------
Since we now have IoEventType in the trunk, I propose we change LoggingFilter
to use a Map<IoEventType,LogLevel> in order to keep the settings for each event
separate. I think that this would become more manageable and easier to
maintain. If a user wants to change the log level just make the call:
loggingFilter.setEventLogLevel( IoEventType.MESSAGE_RECEIVED, LogLevel.DEBUG );
If the user wants to stop logging for an event the call would be:
loggingFilter.setEventLogLevel( IoEventType.SESSION_CREATED, LogLevel.NONE );
We would of course need to create a LogLevel type of NONE.
WDYT??
> LoggingFilter logs exceptionCaught events on error level but uses
> isInfoEnabled in the if-statement
> ---------------------------------------------------------------------------------------------------
>
> Key: DIRMINA-313
> URL: https://issues.apache.org/jira/browse/DIRMINA-313
> Project: MINA
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Niklas Therning
> Assignee: Niklas Therning
> Priority: Minor
> Fix For: 1.0.1
>
>
> Here's the relevant piece of code:
> if( SessionLog.isInfoEnabled( session ) )
> {
> SessionLog.error( session, "EXCEPTION:", cause );
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
