From: <[EMAIL PROTECTED]>
I downloaded and installed a clean Tomcat 5.0.30, and now it started Ok.
So I went back and looked at my other Tomcat 5 install, and found that I
had some commons-xxx jars and log4J among other things in the common/lib
directory. Since we have been suspecious of digester, I removed that one
first - No cigar. I then readded that one and remove the next until I
finally figured out what causes the problem.
There is a compatibility issue between log4j (1.2.8) and Shale. When I
removed my two log4j jars, Shale started ok.
I just added a dependency on log4j-1.2.8 to the use-cases, added
commons-logging.properties and log4j.properties to WEB-INF/classes, built
and deployed it. It starts up normally. That's with the log4j .jar file in
WEB-INF/lib, however.
You mention _two_ log4j jars, which could be a problem. Where were they?
If you have multiple copies of the same class(es) available on the
classpath, strange things can happen.
--
Wendy Smoak
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
