From: fried_chicken <tor...@ya...> - 2006-09-28 18:09:27
|
Hi Jan, I have checked using mvn -X and mvn help:effective-pom, and there are no duplicate or conflicting jetty jars/classes. I've actually deleted org/mortbay directory in my local repository and rebuilt with 6.0.1, and nothing else besides 6.0.1 classes were downloaded. Any additional insight you may have would be appreciated. Again, everything was working fine up until 6.0.0rc1. Since then, I have had this problem. I've been using 6.0.0rc0 in the interim. -fried_chicken Evan, fried_chicken and Steve, The only thing I can think of is that you have conflicting jetty jar versions on your execution classpath. I've tried Steve's code in 6.1-SNAPSHOT and the jetty 6.0 branch and it works fine in both places (of course, I have no idea what is in your webapp, so perhaps the problem lies in there - are you for example configuring the DefaultServlet explicitly?). For those of you using jetty embedded, can you confirm that you have downloaded release 6.0.1 or 6.0.0 (specify which) and have only one copy of each jar on your classpath, all of the same version? For those using jetty via the plugin, can you confirm using mvn -X and mvn help:effective-pom what the jars are on the execution classpath and ensure that there are no duplicates /conflicting versions. cheers Jan evan wrote: > Hi, > Same ClassCastException problem here. Running Jetty 6.0.1 > I was able to fix it by reverting to 6.0.0rc0 > > -evan [snip] -- View this message in context: http://www.nabble.com/Embedded-Jetty%3A-ClassCastException-on-DefaultServlet-tf2320168.html#a6551811 Sent from the Jetty Support mailing list archive at Nabble.com. |