Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 27074 invoked from network); 10 May 2002 22:53:03 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 10 May 2002 22:53:03 -0000 Received: (qmail 19606 invoked by uid 97); 10 May 2002 22:53:09 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 19574 invoked by uid 97); 10 May 2002 22:53:09 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 19562 invoked by uid 98); 10 May 2002 22:53:08 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Date: Fri, 10 May 2002 15:52:57 -0700 (PDT) From: "Craig R. McClanahan" To: Jakarta Commons Developers List Subject: Re: Resisting the temptation In-Reply-To: <5.1.0.14.0.20020511000757.01c3dc08@mail.qos.ch> Message-ID: <20020510154938.Y56198-100000@icarus.apache.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Spam-Rating: localhost 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Sat, 11 May 2002, Ceki G=FClc=FC wrote: > Date: Sat, 11 May 2002 00:24:43 +0200 > From: Ceki G=FClc=FC > Reply-To: Jakarta Commons Developers List > To: Jakarta Commons Developers List > Subject: Re: Resisting the temptation > > At 12:17 10.05.2002 -0700, Craig R. McClanahan wrote: > > > > Another, much more serious worry that I have is the fact that the > > LogFactory > > > class keeps track of LogFactories by classloader. What will happen i= n an > > > environment with multiple classloader per application, eg. EAR classl= oader > > > parent of WAR classloader, parent of JSP classloader, as is the case = in > > > WebLogic and WebSphere? Doesn't Tomcat and other Servlet containers > > > pose the same problem, with to classloaders, the WAR classloader and > > > the JSP classloader? Wouldn't multiple LogFactories, that is multiple > > logging > > > environments be loaded in a single application? > > > > > > What am I missing here? > > > > > > >For Tomcat 4 specifically (and generically for 2.3-based servlet > >containers), the webapp class loader is allowed to look locally first fo= r > >things before delegating. Thus, the current implementation in LogFactor= y > >allows you to put commons-logging.jar and a logging implementation, with= a > >default logging configuration, into common/lib -- but still allow a weba= pp > >to configure its own loggers differently if it wants to (either by > >including a JAR file with the right services entry in WEB-INF/lib, or by > >including a commons-logging.properties file in WEB-INF/classes). Per-JS= P > >class loaders (if the container uses them) will have the webapp class > >loader as the parent, so these JSP pages will see the same logging > >configuration. > > I did not know that the 2-3 spec allowed changes to the classloading > delegation > model. Is it nevertheless accurate to say that each classloader even with= in > the same application will have its own LogFactory implemenation? > Yes. > >Craig > > -- > Ceki Craig -- To unsubscribe, e-mail: For additional commands, e-mail: