I am an unwitting commons logging user [ever since my relatively happy AXIS & happy LOG4J life picked up a third wheel.] I won't waste typing on discussing merits of the choice, I understand the move, but I do feel disheartened that such a simple layer has proved so miserable (pretty impressive ratio of user pain to lines of code. ;-).
Ok, bitch over .... to my problem/point, it is to do with common logging auto-configuration. For all it's intended simplicity, this bootstrap is complicated. Further, and worse, because it is clearly "prior to having a logging sub-system configured" -- is hellish to debug, since absolutely no log message come out. Please please please find a way to have commons logging squeak when it fails --- System.out would be fine. Tell me where the commons-logging properties file is being looked for, tell me if the log4j.properties file (annoying to have to have a separate one of these for commons) is found or not, and where. Tell me if an attempted instantiated class failed to load, tell me something. All I get is 'NullPointerException' as a Log object is failed to be returned 'cos some lower level failed. This looses the root cause of the problem, and has me guessing -- and I've lost hours to it. :-( I know log4j does not like to be verbose to stdout, but commons logging has (for me) failed during almost all first few start-ups. Whilst it matures, and hopefully stabilizes, please have the default behaviour be debug on start-up to stdout -- and allow folks to turn that off if they chose. Pretty please. ;-) FWIIW: Today's problem is that my environment (the Sybase application server) is returning a null for the Logger class loader [valid per my reading of the JDK 1.3 docs, to imply "Bootstrap Class Loader".] Since commons is (at least in the first drop of source I read) using this as a key to a factories Hashtable [and Hashtable barfs on a null key] thing die. I am not expert enough to know if there is a solution (i.e. if null call ClassLoader.getSystemClassLoader()) or if that leads to future Class cast problems. If somebody has an idea of a real fix please let me know. Until then I'll be hacking around building common logging [deleting the JDK 1.4 stuff since I'm not so favoured] and trying what I can. Thanks in advance for any feedback, and/or for listening to me whine. ;-) regards Adam -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
