Berin Loritsch dijo: > Carsten Ziegeler wrote: >> So, my suggestion is to: >> - deprecate the use of LogKit >> - switch to log4j as default >> - make it possible to configure log4j from within Cocoon (like the >> current logkit.xml for LogKit). >> >> WDYT? > > My only suggestion is to have a way of differentiating the logkit.xml > for LogKit and the config file for Log4J. Either log4j.xml or > logging.log4j would be great. The thing is that Log4J comes with code > to parse and configure itself from an XML file whereas LogKit has that > as an add-on library.
Good! I have a question too: What happen when we currently have more than one jars that implement his own log4j configuration? Will it work? Best Regards, Antonio Gallardo
