First there was System.out and System.err. But they were inflexible, so a need for a feature-rich logging has arisen (note that I was in elementary school at that time). Logging that can be customized format, that can go to multiple targets – files, consoles, emails, etc. So log4j has appeared – in 1999.
But other solutions spawned as well, including java.util.logging – an attempt to have standard JDK logging. Note a very successful attempt, as it turned out. java.util.logging appeared with JDK 1.4 in the beginning of 2002. A few months later the realized need for a common logging interface for all existing loggers resulted in apache common-logging.
The idea of commons-logging was viable – libraries should not force a particular logging implementation on applications that use them. So each logging implementation gets adapted to a common API which is used by the library – so your library does not use org.apache.log4j.Logger – it uses org.apache.commons.logging.Log, and it delegates to whatever logging framework exists on the classpath. That way your project can use multiple libraries and use a single logging configuration for all of them.
But commons-logging was not good enough. People say that it has caused more problems than it has solved. So the author of log4j – Ceki Gülcü created a new project – slf4j (Simple Logging Facade for Java) in 2005. It aims to be a better commons-logging.
Log4j has been widely used since 1999, but it was not good enough, so guess who created a new project – logback. It was Ceki Gülcü again. Why a new project? Well, combination of political reasons and old code base that needs replacing from the ground, I guess. Anyway, logback appeared in 2006. How it is better than log4j? Ceki explains here.
So back to present day – there are a lot of logging frameworks and two facades – commons-logging and slf4j. Every library uses a different one, and it’s a mess. Version mismatches, tons of Logger classes on the classpath. Maven succeeds at making this simpler by at least not allowing multiple versions of the same logging implementation, but that’s it. And if you don’t know all the history above and which framework is used for what, it is likely for your project to suffer from that mess.
What’s the solution? The simplest thing is to use slf4j and logback. Why?
- slf4j has bridges for many existing implementations. This means that you remove the log4j.jar and use the log4j-over-slf4j.jar – it has the same classes in the same package, only the implementation differs – it delegates to the current slf4j implementation in use. That way all libraries that use log4j (or any other bridged implementation) will work with your logback configuration. Unfortunately this doesn’t work quite well with java.util.logging, so you have to hope not to have too many libraries that have decided on a “minimal dependency footprint”.
- logback is better than log4j (same author – newer implementation, learning from previous mistakes)
- if a better framework than logback appears you can easily switch to it without changing your classes.
And finally, a word about the logging configuration. It should be external, in the same way (and the same location, preferably) as the other externalized project configurations. You should then load it based on a system “config.location” property.
(In a spring-based web-application there is
Log4jWebConfigurer, but there isn’t
LogbackWebConfigurer. Luckily, it is simple to write, and there are some existing implementations that are based on the log4j one. In your web.xml the
logbackConfigLocation param should be:
Why something so simple became so complicated? Because it isn’t simple. There are too many factors that were not taken into account in the beginning, so they needed to be rectified later. It’s a good thing that there hasn’t been a major change in the field since 2006, so we can consider things stable.
Related Articles :
Bulletproof Java Code: A Practical Strategy for Developing Functional, Reliable, and Secure Java Code
Use Java? If you do, you know that Java software can be used to drive application logic of Web services or Web applications. Perhaps you use it for desktop applications? Or, embedded devices? Whatever your use of Java code, functional errors are the enemy!
To combat this enemy, your team might already perform functional testing. Even so, you're taking significant risks if you have not yet implemented a comprehensive team-wide quality management strategy. Such a strategy alleviates reliability, security, and performance problems to ensure that your code is free of functionality errors.Read this article to learn about this simple four-step strategy that is proven to make Java code more reliable, more secure, and easier to maintain.