Matt, My apologies in advance for newbie questions...
I am experiencing the same exception, however my skeleton app runs fine in Jetty. I try to run it in Netbeans with the embedded Tomcat and the exception described here occurs. I successfully ran the skeleton in a standalone Tomcat 5.5.23 by deleting the old ehcache jars and copying in a freshly downloaded 1.3.0 (not beta 3). I try the same in my netbeans project folders, but the 1.2.3 jar keeps coming back (probably due to maven auto-downloading it?) and the app blows up. I presume the pom.xml controls what is downloaded, but I am not seeing the ehcache 1.2.3 reference that I need to change. How exactly do I need to change my pom.xml to use 1.3.0 (or beta 3) and stop including the faulty 1.2.3? Many thanks, Jim I believe this is caused by having an old version (1.2.3) of EhCache in your classpath. If you manually add EhCache 1.3.0-beta3 to your pom.xml, it should fix the problem. Matt On 6/6/07, thinkboy <[EMAIL PROTECTED]> wrote: > > hi , I got an exception after a brand new try on 2.0 m5 > -- View this message in context: http://www.nabble.com/2.0-M5%3A-many-exception-after-new-installation-%3E-%24mvn-jetty%3Arun-war-tf3876663s2369.html#a11166341 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
