I've submitted patch 28860. I realize this is after the code freeze, but I'd prefer to see this patch instead of the current code. If 2.1.5 goes out with the current code we would have to maintain the current behavior of logger-type.
Ralph -----Original Message----- From: Carsten Ziegeler [mailto:[EMAIL PROTECTED] Sent: Saturday, May 08, 2004 12:34 AM To: [EMAIL PROTECTED] Subject: RE: LogKitLoggerManager I guess the only reason is lazyness :) I think it should work and yes I think perhaps adding a parameter to web.xml should do the configuration trick. Carsten ________________________________ From: Ralph Goers [mailto:[EMAIL PROTECTED] Sent: Saturday, May 08, 2004 8:13 AM To: '[EMAIL PROTECTED]' Subject: LogKitLoggerManager Currently, CocoonServlet.java performs a new LogKitLoggerManager. I would like to use a different LoggerManager. Is there any reason this couldn't be made configurable. If so, would the best place be from the servlet context? Ralph
