Hello zarathustra, Sorry if this is stating the obvious, but it looks like a classpath issue, are you sure that the wicket jar is being included in your servlet's lib directory?
One way to find out what's in your classpath is to simply print it out with a jsp: Try saving the following as a jsp file and then put it in the root context of your servlet, remove any references to wicket or the wicket filter (in the web.xml file) and then see if the jsp prints out the wicket jar myclasspath.jsp then point to it http://localhost:8080/myclasspath.jsp (or http://localhost:8080/myappcontext/myclasspath.jsp or whatever) it should print out the wicket.jar and the wicket-extensions.jar Hope this helps Cheers Simon -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/ClassNotFoundException-I-m-out-of-ideas-tp4652049p4652054.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
