commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Costin Manolache <cmanola...@yahoo.com>
Subject Re: JNDI based selection
Date Wed, 11 Dec 2002 17:56:49 GMT
Ceki Gülcü wrote:

> 
> I have been a long time critic of commons-logging API for its class
> loader based approach of selecting the logging implementation. See for
> example my http://qos.ch/logging/thinkAgain.html document. I think
> more reliable solutions exist. In particular, you might want to
> consider the JNDI based solution discussed in
> http://qos.ch/logging/sc.html.

The class loader based _default_ approach is not perfect, but
you can plug other factories. 

I like the JNDI solution, excelent idea. 

One comment: application isolation is not a voluntary thing. If we want to 
isolate the loggers you can't allow the application to specify what logger 
it wants in web.xml and hope they'll not use the same name. 

Using java:env is a great solution, probably it needs an external
config ( server.xml or the logging config file ).

Costin


> 
> 
> I suggest that you begin reading "thinkAgain.html" first and then read
> sc.html. You are welcome to use the heretical ideas contained therein
> to your advantage or alternatively ignore them altogether. Your
> comments, constructive or otherwise, are welcome.
> 
> Regards,
> 
> --
> Ceki




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


Mime
View raw message