Having given more consideration to this, I'm now of the opinion that Jetty shouldn't be catching the NoClassDefFoundError. It is an Error, not an Exception, and as such, is indicating serious trouble: multiple versions of the same jar leave the way open for all sorts of wierd and unexpected behaviour. Better to flag it up front with a visible failure IMHO.
Jan Dave Smith wrote: > Ding,Ding,Ding . Scott wins the prize. Duplicate jar in the deploy > directory and in the ear. So do we just need to make sure this > documented or should Jetty catch both exceptions? > > Scott M Stark wrote: > >> A ClassNotFoundException is not being thrown because the class >> being loaded is found in the JBoss classloader space, but that >> class has a static reference to the org/apache/cactus/ServletTestCase >> and this apparently is not in the JBoss classloader space and so >> a NoClassDefFoundError results during linking. Most likely there >> are duplicate jars in the classpath with inconsistent contents. >> >> xxxxxxxxxxxxxxxxxxxxxxxx >> Scott Stark >> Chief Technology Officer >> JBoss Group, LLC >> xxxxxxxxxxxxxxxxxxxxxxxx >> >>> [junit] org/apache/cactus/ServletTestCase >>> [junit] java.lang.NoClassDefFoundError: >>> org/apache/cactus/ServletTestCase >>> [junit] at java.lang.ClassLoader.defineClass0(Native Method) >>> [junit] at >>> >> java.lang.ClassLoader.defineClass(ClassLoader.java:493) >> >>> [junit] at >>> java.security.SecureClassLoader.defineClass(SecureClassLoader >>> .java:111) >>> >> >> >> >> _______________________________________________ >> Jboss-development mailing list >> [EMAIL PROTECTED] >> https://lists.sourceforge.net/lists/listinfo/jboss-development >> >> > > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
