Hi, I guess the subject pretty much says it all. I've been seeing a ton of issues people have when trying to use commons-logging. Some have to do with tomcat and complicated classloader issues, some have to do with apps that just use commons-logging (e.g. struts) and so users don't have the option to NOT use commons-logging.
My question is, can we, should we, do anything to make log4j and commons-logging play better with each other? Or it is not log4j's job? Or is there nothing log4j can do about it? Personally, having used log4j for a long time and loving it, and having tried commons-logging a couple of times, I like using log4j by itself. I don't think the added complexity (configuration, deployment) of commons-logging is worth the effort at all. What do people think? Yoav Shapira Millennium ChemInformatics This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
