Hmmm.... The difficulty here seems to be in that the proper use if not easy to understand, and that the thought in "well thought out" doesn't seem to be documented (at least I didn't see it after a quick glance). If someone can point the way to the mail threads that covered the "thinking" process, I'd willingly take a stab at trying to capture those thoughts onto paper (or virtual paper as the case may be), and submit it back to the list. The distillation of a newcomer to the discussion (any of the other new comers could also do this) would probably help to identify which parts of the thought process would be difficult for others to understand.
I'm sure the JCL works well in many situations, and certainly for the situations it was specifically designed to handle (servelet containers, etc). It may work well for all situations, but it appears that the "how" of that is not really clear to new users. Let's try and clarify the how, and then see what the feeling is on classloading, etc. -AMT -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, November 03, 2003 5:36 AM To: [EMAIL PROTECTED] Subject: DO NOT REPLY [Bug 24353] - Log interface should be loaded by loadClass method DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24353>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24353 Log interface should be loaded by loadClass method [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2003-11-03 13:35 ------- I disagree with this. If used properly, you'll see that commons-logging classloading handling is well thought out, and works perfectly well. Pesonally, I am against the change you propose. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
