Yes, I've read all that. Those links are well known. But please carefully read from the link you provided...
Stian Soiland wrote:
http://radio.weblogs.com/0122027/2003/08/15.html "Commons Logging was my fault"
"If you're building a stand-alone application, don't use commons-logging. If you're building an application server, don't use commons-logging. If you're building a moderately large framework, don't use commons-logging. If however, like the Jakarta Commons project, you're building a tiny little component that you intend for other developers to embed in their applications and frameworks, and you believe that logging information might be useful to those clients, and you can't be sure what logging framework they're going to want to use, then commons-logging might be useful to you."
That's what RESTlet is, a library/component to be embedded into other setups. If I'm using log4j, I want _all_ my log messages to go through log4j. That's the WHOLE purpose of using the Commons Logging facility (with all its problems).
Adam
