FAQ
Some frequently asked questions are:
- How do I see Tedhi logs?
- Why do I get a 'Failed to load class "org.slf4j.impl.StaticLoggerBinder"' message?
How do I see Tedhi logs?
Tedhi uses SLF4J for logging. Accessing logging from Tedhi involves a couple of steps:
- Add the slf4j binding for your favourite logging framework (eg: slf4j-log4j.jar)
- Enable DEBUG level logging for the following category: net.sourceforge.tedhi.
Why do I get a 'Failed to load class "org.slf4j.impl.StaticLoggerBinder"' message?
Tedhi uses SLF4J for logging. This means that you can enable Tedhi logging if you wish. SLF4J is a logging facade, which is great because it means you can use your favourite logging framework to output Tedhi's log messages. Unfortunately SLF4J emits the following warning message if there is no slf4j implementation binding (ie: you're missing slf4j-log4j12-x.x.x.jar if you're using log4j):
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
- if you want to see Tedhi logging, follow the steps in "How do I see Tedhi logs?", or
- include the 'no-op' slf4j binding (slf4j-nop-x.x.x.jar).