Error messages like the one you encountered are not actually based on class path ordering ... they are caused when there is more than one copy of the class visible in the class loaders hierarchy. You should always ensure that, if a set of classes is visible in the servlet container's class loader (such as being in "common/lib" in Tomcat), you should *not* also have those classes in your /WEB-INF/lib directory. This gets more difficult to manage when you're using an IDE -- unfortunately, I am not familiar enough with how NetBeans does its Tomcat integration to offer any specific advice here.What is the proper order for the jars in the class path. Sometimes I get the error org.apache.commons.logging.impl.Jdk14Logger.class does not implement Log class. Sometimes I do not get the error. I can just restart Tomcat and the exception goes way. Is there some unsychronized threading issue in the startup code?
I'm running the Tomcat 4.0.6 under NetBeans 3.5.1 with Struts 1.1. Any issues there?
However, Tomcat 4.0.x has issues in its class loading implementation ... a more up-to-date version (4.1.29 or 5.0.19) would be my strong recommendation.
Craig
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
