> 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
.
-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
> 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
>
mcat 6.x, or am
I wrong ?
Thanks a lot,
Rogerio Baldini
jCompany Suite - Product Owner
+55 (31) 3555-0050
[EMAIL PROTECTED]
Powerlogic S.A.
-Mensagem original-
De: David Delbecq [mailto:[EMAIL PROTECTED]
Enviada em: terça-feira, 12 de fevereiro de 2008 09:20
Para: Tomcat Users List
As
Tomcat Users List
Assunto: Re: Tomcat6 classloader problem
Root of your problem is that: "You have more than one version of
'org.apache.commons.logging.Log' visible"
You say app1 access app2 which access back app1. Webapps in a container
should not be able to see each other
Root of your problem is that: "You have more than one version of
'org.apache.commons.logging.Log' visible"
You say app1 access app2 which access back app1. Webapps in a container
should not be able to see each other's classes. Can you tell us which
method you used to have those 2 webapps see e
Hi,
I am passing through this problem nowadays in Tomcat6:
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException:
Invalid class loader hierarchy. You have more than one version of
'org.apache.commons.logging.Log' visible, which is not
