Hi Vincent,
You are probably not doing anything wrong and it most probably a log4j
problem. In log4j 1.2 beta2 and earlier versions there was a serious
compatibility problem where code compiled with log4j 1.1.3 would not
run with log4j-1.2x.jar. However, the same code would compile and run
fine
h regard to what you are doing wrong...it usually starts when you
listen to people like me :-)
John
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 27, 2002 7:11 PM
To: 'Log4J Users List'
Subject: [The plot continues] org/apache/log4
..]
- Original Message -
From: "Vincent Massol" <[EMAIL PROTECTED]>
To: "'Log4J Users List'" <[EMAIL PROTECTED]>
Sent: Wednesday, February 27, 2002 5:11 PM
Subject: [The plot continues] org/apache/log4j/Logger NoClassDefFoundError with
version 1.1.3
Following the thread "org/apache/log4j/Logger NoClassDefFoundError with
version 1.1.3" here are my findings (and more questions) :
1/ I am using Log4j in a WAR application (inside an EAR) in WL 6.1 SP2
2/ I tested the following structure :
myear.ear
|_ mywar.war
|_ WEB-INF/lib
|_ cac
