Hi Bill,
That's very good news.
BTW, have you considered JNDI based RepositorySelector? See
https://www.qos.ch/logging/sc.html#jndi-1
Wouldn't we get rid of all the class loader problems and solve the
separation problem at the same time?
At 12:20 PM 4/24/2003 -0700, Bill Barker wrote:
>It doesn't seem to have gotten in the nightly yet. It's at
>http://cvs.apache.org/viewcvs/jakarta-tomcat/proposals/Log4jHelper/
>
>----- Original Message -----
>From: "Ceki Gülcü" <ceki@qos.ch>
>To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
>Sent: Thursday, April 24, 2003 5:00 AM
>Subject: Re: Why commons-logging-api.jar?
>
>
>
>After downloading Tomcat 3.3.1a, I could not find any log4j related
>jar files.
>
>Regardless, for Tomcat 4.x which has a non-delegating class loader
>model, what can be the technical reason for putting
>commons-logging-api.jar in commons/lib/?
>
>Especially in light of numerous problems with unfound factories,
>incompatible classes, unimplemented methods, ... all of which are
>class loader related.
>
>I am stumped.
--
Ceki For log4j documentation consider "The complete log4j manual"
http://www.qos.ch/shop/products/clm_t.jsp
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
|