tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "GOMEZ Henri" <hgo...@slib.fr>
Subject RE: PROPOSAL: Consistent logging ( for 3.x, 4.x )
Date Thu, 06 Jun 2002 08:18:57 GMT
>What I'm proposing is to gradually cut down to one logger API
>( commons-logging ) and the 2 major implementations ( log4j and
>jdk1.4 ) and the associated ( and well-documented/well known )
>config files.

+1

>This may take a long time, but there are few steps that we 
>can ( should ) take for the next releases ( 4.1.0 and 3.3.3 ).
>Most of those are cosmetic ( i.e. minimal code changes ):
>
>1. Include log4j.jar in the distributions. 

What about commons-logging, it's present in JTC and TC 4.0.
Should it be present in TC 3.3/4.0/4.1 and JTC ?

>2. In util, make o.a.t.util.Log use commons-logging as backend
>by default.
>
>3. In 3.3, remove the configs for queue-logging. That will make
>all 3.3 use the default logger, which in turns use commons-logging.
>
>4. Eventually provide a small fix in 4.x so that LoggerBase 
>defaults to commons-logging if no other logger is specified,
>and don't specify any logger in the config file.
>
>5. Same for jasper ( that's the most urgent, as it's logger
>is the worst ).
>
>In all cases the explicit setting in server.xml will activate 
>the current logger.
>
>
>Long term ( for next releases ):
>
>- replace the use of the old loggers to direct calls to commons-log.
>
>- other advanced stuff, like advanced configurations 
>
>Opinions ?

go go go

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message