[
https://issues.apache.org/jira/browse/DIRMINA-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Therning resolved DIRMINA-314.
-------------------------------------
Resolution: Fixed
SessionLog.setLogger(session, logger) and SessionLog.setPrefix(session, prefix)
have been added. The default logger used by SessionLog has been changed. It'll
now append .SessionLog to the name of the IoHandler class and use that as the
name of the default logger.
The log level used by LoggingFilter can now be changed using
LoggingFilter.setDefaultLogLevel() and
LoggingFilter.setExceptionCaughtLogLevel(). The defaultLogLevel will be used
for all events except exceptionCaught which will use the
exceptionCaughtLogLevel. The default is INFO for both of them.
LoggingFilter will use different loggers for each event. This makes it simpler
to filter out unwanted events. The default prefix for the loggers is the name
of the logger used by SessionLog (e.g.
org.apache.mina.example.echoserver.EchoProtocolHandler.SessionLog.sessionOpened).
> LoggingFilter should use different loggers for each event and the logger
> prefix and level should be configurable
> ----------------------------------------------------------------------------------------------------------------
>
> Key: DIRMINA-314
> URL: https://issues.apache.org/jira/browse/DIRMINA-314
> Project: MINA
> Issue Type: New Feature
> Reporter: Niklas Therning
> Assigned To: Niklas Therning
> Priority: Minor
> Fix For: 2.0.0-M1
>
>
> It would be nice to be able to set my own logger name for LoggingFilter to
> use. It can be done today by setting an attribute in my session but then the
> prefix used by SessionLog will be null.
> It would also be nice to be able to set the log level to be used. Currently
> the level is always INFO.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
