Hi Francis, Rainer. >> Besides the prepared statement fixes we should reconsider the slf4j logging >> (already tried but the problem seems to be the configuration) and the >> exception handling - and maybe a few more things. > > I'm a fan of slf4j, and so dumping commons-logging. But the main > problem is that we have a hard dependency on log4j. We should at least > make that optional.
Why don't you have a look at Logback (+slf4j): http://logback.qos.ch/documentation.html It is API compatible with slf4j, works with any logging impl out there (jdk, commons, ...) and even writes to stdout if no impl is available (handy for unit tests). Moreover it gives you the possibility to keep the old calls to log4j in the source, if this is really necessary: http://slf4j.org/legacy.html Cheers, Andi. -- web: http://andreasfink.com/ mail: [email protected] mobil: +34 65 1728443 tel: +34 93 2082949
