What is the issue with the runtime discovery algorithm of Apache Commons Logging
Dave Syer (SpringSource) writes in his blog:
Unfortunately, the worst thing about commons-logging, and what has made it unpopular with new tools, is also the runtime discovery algorithm.
Why? What is the issue with its runtime discovery algorithm? Performance?
Answer
Why? What is the issue with its runtime discovery algorithm? Performance?
No, it's not performance, it's classloader pain. JCL discovery process relies on classloader hacks to find the logging framework at runtime but this mechanism leads to numerous problems including unexpected behavior, hard to debug classloading problems resulting in increased complexity. This is nicely captured by Ceki (the author of Log4J, SLF4J and Logback) in Think again before adopting the commons-logging API (which also mentions memory leaks problems observed with JCL).
And this is why SLF4J, which uses static bindings, has been created.
Ceki being the author of SLF4J, you might think his articles are biased but, believe me, they are not and he is providing lots of references (evidences) to prove his point.
To sum up:
- Yes, JCL is known to be broken, better stay away from it.
- If you want to use a logging facade (not all projects need that), use SLF4J.
- SLF4J provides a JCL-to-SLF4J bridge for frameworks still using JCL like Spring :(
- I find Logback, Log4J's successor, to be a superior logging implementation.
- Logback natively implements the SLF4J API. This means that if you are using Logback, you are actually using the SLF4J API.