cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <Ralph.Go...@digitalinsight.com>
Subject RE: LogKitLoggerManager
Date Sun, 09 May 2004 07:07:45 GMT
Carsten,

I just downloaded the most recent source and noticed you modified this
section of code just last week to add support for log4j. Do I need to
maintain compatibility with logger-type or can I just take that out? The
problem is the code assumes that if logger-type is not "logkit" that it must
be log4j.  I was thinking of using "logger-class" as the init parm, but I
could use logger-type if that is preferable, however if specified it would
be the name of the class that implements LoggerManager. If not specified,
then logkit would be used.

Ralph

-----Original Message-----
From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de] 
Sent: Saturday, May 08, 2004 12:34 AM
To: dev@cocoon.apache.org
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:Ralph.Goers@digitalinsight.com] 
	Sent: Saturday, May 08, 2004 8:13 AM
	To: 'dev@cocoon.apache.org'
	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


Mime
View raw message