[
https://issues.apache.org/jira/browse/DIRMINA-821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018209#comment-13018209
]
Emmanuel Lecharny commented on DIRMINA-821:
-------------------------------------------
The pont is that usually, users have their own logger implementation selected
prior using MINA, which is just a framework. Providing an implementation is
just out of question, because it may generate some conflicts
Regarding the addition in a README or whatever document you suggest, I would
just say that any place we can select to add such warning is a vain attempt to
workaround the famous RTFM :-)
Users don't read manuals, or documentation.
As a matter of fact, the MINA web site has a FAQ
(http://mina.apache.org/faq.html) with a "How do I...?" item, and a paragraph
about "How can I let MINA log messages using my favorite logging framework
(i.e. Log4J)?"...
> Wrong binding jar for slf4j in distribution
> -------------------------------------------
>
> Key: DIRMINA-821
> URL: https://issues.apache.org/jira/browse/DIRMINA-821
> Project: MINA
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.2
> Reporter: Zsolt Kúti
> Labels: logging
>
> On startup my app this error pops up:
> java.lang.ClassNotFoundException: org.slf4j.impl.StaticLoggerBinder
> The classpath has the following jars from the distribution's lib dir:
> slf4j-api-1.5.11.jar
> jcl-over-slf4j-1.5.11.jar
> commons-logging-1.0.3.jar
>
> slf4j site claims this exception is thrown when no binding is
> available.
> It also calims that slf4j-jcl-xxx.jar is the binding for Jakarta
> Commons Logging. This binding will delegate all SLF4J logging to JCL.
> Having put this component on classpath resolves the issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
