On Fri, 2002-07-26 at 10:59, Gerard van Enk wrote: > Michiel Meeuwissen wrote: > > Er, I accidently seem to have checked in my build.xml, which means that the > > current build uses log4j 1.2.4 rather than 1.1.3. Log4j 1.2 is the latest > > stable version, so it not such a bad change after all, but well, it was an > > accidental change, so I probably should roll it back. > > > > Especially because I had trouble getting it rolling with tomcat (mysterious > > classloader issues), but perhaps this is a good opportunity for tomcat-users > > to help us out here. Eventually I think we want to switch to the latest > > version anyway. Orion uses crimson.jar to work with log4j 1.2.x When crimson is removed on an orion server, the same error occours.
We need to do some research on the following question: Is crimson needed by log4j+ (we already have xml-api's, xerces, xalan,crimson is not mentioned in xalan package.. Do we need another jar instead of crimson or is this a log4j+ bug? (or maybe a xerces bug) Crimson can be found at the following url: http://xml.apache.org/dist/crimson/crimson-1.1.3-bin.tar.gz. i didnt tyr if it worked with tomcat 4,... but the people who like to test it can :) -- Eduard Witteveen Systeem Ontwikkelaar NOS Internet, Gateway C Kamer 107 +31(0)356772910 http://www.omroep.nl/ Sed quis custodiet ipsos custodes? : The sixth Satire from Juvenal
