Just curious...what if in example one you make this change change to
your LogService()....
Class.forName("org.apache.log4j.PropertyConfigurator");
to
Class.forName("org.apache.log4j.Category");
2/ Should still get the nothing happens.
(I am not convinced that you are rid of 1.2 yet :-) )
Maybe somewhere there is a Category class hanging around somewhere...
After that..try...
Object o = Class.forName("org.apache.log4j.Category").newInstance();
and
Object o =
Class.forName("org.apache.log4j.PropertyConfigurator").newInstance();
I think the first one may fail but you could put a
static { out.println(" Version 1.1.3"); } in your 1.1.3 classes to make
sure you really are loading the right version..
If I am speaking crazy talk it's because it's 2.40am and I don't work
nights and I am a total hack.
With 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/log4j/Logger
NoClassDefFoundError with version 1.1.3
2/ I tested the following structure :
myear.ear
|_ mywar.war
|_ WEB-INF/lib
|_ cactus.jar
|_ WEB-INF/classes
|_ classes called by cactus.jar
This worked fine (there was no log4j.jar and cactus does not try to log
if log4j is not in the classpath).
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
