From: Christoph S. <ste...@ic...> - 2001-10-08 09:02:03
|
Egon Willighagen wrote: > > Hi all, > > there was been some discussion on Log4J in the past (a year ago?), > and i've implemented use of Log4J in JChemPaint-CDK. > > It is easy to implement, is very configurable and basically works > great. Some features: > > - logging of time per log line -> we can do performance tests more easily > - log lines have a LEVEL (as in syslog): ERROR, INFO, WARN, DEBUG etc > - logging to file or stdout > > I want to propose to use it in the CDK libs as well. But in such a way > that if the log4j jars are missing, no harm is done. (For the low profile > implementations using cdk, jcp-applet etc). > > Proposal: CDKLogger.java > logs to /dev/null if log4j.jar is not in classpath > logs to logj4 if log4j.jar is in classpath > > Comments, ideas? Sorry for the late reply. Mail was broken. I have tried log4j for my CASE* programs where optimum performance is essential and was not sure whether the slowdown due to logging was acceptable, but in the case of JCP-CDK that should not be a problem. The CDKLogger wrapper is a good idea. Cheers, Chris * Computer Assisted Structure Elucidation -- Dr. Christoph Steinbeck (http://www.ice.mpg.de/departments/ChemInf) MPI of Chemical Ecology, Carl-Zeiss-Promenade 10, 07745 Jena, Germany Tel: +49(0)3641 643644 - Fax: +49(0)3641 643665 What is man but that lofty spirit - that sense of enterprise. ... Kirk, "I, Mudd," stardate 4513.3.. |