Re: JNDI based selection

2002-12-12 Thread Costin Manolache
Ceki Gülcü wrote: > OK, the solution I presented solves the "VOLUNTATRY separation of > logging" problem. It can be further refined to address the > "MANDATORY separation of logging" problem Costin mentions. > Costin suggested the use of string prefixes to enforce mandatory > separation which is

Re: JNDI based selection

2002-12-12 Thread Ceki Gülcü
Costin Manolache wrote: > 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. OK, the solution I presented solves the "VOLUNTATRY se

Re: JNDI based selection

2002-12-11 Thread Costin Manolache
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

JNDI based selection

2002-12-11 Thread Ceki Gülcü
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 solu