Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>We use <a href="http://www.slf4j.org/" rel="noreferrer">SLF4J</a> on our current project and it's worked very well for us. SLF4J is written by Ceki Gülcü, the creator of Log4J, and he's done a really great job. In our code we use the SLF4J logging APIs directly, and we configure SLF4J so that calls from the <a href="http://commons.apache.org/logging/" rel="noreferrer">Jakarta Commons Logging</a> (JCL), java.util.logging (JUL), and <a href="http://logging.apache.org/log4j/1.2/index.html" rel="noreferrer">Log4J</a> APIs are all bridged to the SLF4J APIs. We need to do that because like you we use third party (open source) libraries that have chosen different logging APIs.</p> <p>On the bottom of SLF4J, you configure it to use a particular logger implementation. It comes with an internal, or "simple" logger, and you can override this with Log4J, JUL, or <a href="http://logback.qos.ch/" rel="noreferrer">Logback</a>. Configuration is all done simply by dropping in different jar files in your classpath.</p> <p>Originally, we used the Logback implementation, also written by Ceki Gülcü. This is very powerful. However, we then decided to deploy our application to the Glassfish Java EE application server, whose log viewer expects JUL-formatted messages. So today I switched from Logback to JUL, and in just a few minutes I replaced two Logback jars with an SLF4J jar that connects it to the JUL implementation.</p> <p>So like @overthink, I would heartily recommend using SLF4J in your setup.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload