Hi all- I am using Tomcat (as part of JSWDP1.3) and would like to pre-compile my JSPs with Jasper2 in my Ant script. Jasper2 requires "commons-logging.jar", which, for some unexplicable reason, starts asking for classes in "log4j.jar" (why is this idiotic behaviour of "commons-logging.jar"?) . I end up with this exception from Jasper2 (attached below). I do not want to use log4j, but If I dare to include "log4.jar" in the Jasper2 task classloader, another tasks (Xdoclet) becomes aware of it (despite the fact that I use separate Ant classloader for it!) and starts throwing log4j-related configuration exceptions. Please, help me out of this mess! A suggestion: Please, get rid of both commons-logging.jar and log4j.jar - jdk1.3 is dead! Hristo ---------------------------------------------------------------- [jasper] Caused by: org.apache.commons.logging.LogConfigurationException: org .apache.commons.logging.LogConfigurationException: No suitable Log constructor [ Ljava.lang.Class;@ec6b00 for org.apache.commons.logging.impl.Log4JLogger [jasper] at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(Lo gFactoryImpl.java:532) [jasper] at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(Lo gFactoryImpl.java:272) [jasper] at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(Lo gFactoryImpl.java:246) [jasper] at org.apache.commons.logging.LogFactory.getLog(LogFactory.java: 395) [jasper] at org.apache.jasper.compiler.Compiler.<clinit>(Compiler.java:97 )
--------------------------------- Do you Yahoo!? Exclusive Video Premiere - Britney Spears