Not sure if this was mentioned, but you should configure your app to use
commons-logging and then specify in its configuration to use Log4j. That
way you can swap out logging implementations by simple configuration and
library addtions/removal (no recompile necessary).
At the risk of quibbling, I would dispute this as a general rule; commons-logging is great for library packages which may be used in a variety of contexts, but unless you're writing a Struts application for general distribution and re-use, there's less justification for using commons-logging universally.
There's nothing wrong with using commons-logging in applications and other more finished products, but commons-logging is a greatly simplified API (for good reason) and in an application, you may find it worthwhile to commit to a more sophisticated logging tool (like Log4J) in order to have more powerful logging features.
Joe
--
Joe Germuska
[EMAIL PROTECTED]
http://blog.germuska.com
"We want beef in dessert if we can get it there."
-- Betty Hogan, Director of New Product Development, National Cattlemen's Beef Association
smime.p7s
Description: S/MIME cryptographic signature
