RE: RES: Tomcat6 classloader problem

> From: Rogerio Baldini das Neves > [mailto:[EMAIL PROTECTED] > Subject: RES: RES: Tomcat6 classloader problem > > Then, the solution is putting the commons-logging jar in tomcat lib > directory, right ? Maybe. My preferred choice would be for the shared classes not to us

RES: RES: Tomcat6 classloader problem

. -Mensagem original- De: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Enviada em: terça-feira, 12 de fevereiro de 2008 13:00 Para: Tomcat Users List Assunto: RE: RES: Tomcat6 classloader problem > From: David Delbecq [mailto:[EMAIL PROTECTED] > Subject: Re: RES: Tomcat6 classloader p

RE: RES: Tomcat6 classloader problem

> From: David Delbecq [mailto:[EMAIL PROTECTED] > Subject: Re: RES: Tomcat6 classloader problem > > From http://tomcat.apache.org/tomcat-6.0-doc/logging.html : > "Tomcat 6.0 uses Commons Logging > <http://commons.apache.org/logging> throughout its internal >

Re: RES: Tomcat6 classloader problem

From http://tomcat.apache.org/tomcat-6.0-doc/logging.html : "Tomcat 6.0 uses Commons Logging throughout its internal code allowing the developer to choose a logging configuration that suits their needs," Could it be this class is exposed to webapps? En l'i

RES: Tomcat6 classloader problem

Hi David, In truth ,I have a library in tomcat lib directory to communicate both applications. Using the resource: There are 2 'org.apache.commons.logging.Log' visible. One in app1 and another in app2. But no one in tomcat lib directory. I don't want to put in there because of possibl