[ http://issues.apache.org/jira/browse/DIRMINA-233?page=comments#action_12424884 ] peter royal commented on DIRMINA-233: -------------------------------------
Perhaps the words "logging abstraction" are the wrong ones. MINA has two places where it principally logs (the other 2-3 lines can be removed): http://svn.apache.org/viewvc/directory/trunks/mina/core/src/main/java/org/apache/mina/util/SessionLog.java?view=markup http://svn.apache.org/viewvc/directory/trunks/mina/core/src/main/java/org/apache/mina/common/support/DefaultExceptionMonitor.java?view=markup The ExceptionMonitor is already pluggable. The SessionLog is not. What I would propose is the "Logger" mechanism in the SessionLog is implemented similarly to theExceptionMonitor so that one could easily plug in a SessionLog implementation that goes to the log toolkit of choice. Thus MINA would have *NO* dependency on any logging abstraction. Having an extra dependency just for this small usage isn't necessarily worth it, and complicates things for users. > Provide an extra thin logging layer for those who don't want SLF4J > ------------------------------------------------------------------ > > Key: DIRMINA-233 > URL: http://issues.apache.org/jira/browse/DIRMINA-233 > Project: Directory MINA > Issue Type: Task > Reporter: Trustin Lee > > As MINA gets more and more popular, the number of people who doesn't want > SLF4J increased because they were using other logging frameworks such as > Log4J or commons-logging. We know SLF4J provides what exactly Log4J or > commons-logging provides, but it's just a matter of preference. We need to > meet as many people's preference as we can as a general network application > framework. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
