It should be nothing more than a warning; using servlets is still
legal, but we just think using filters is a better idea.
Eelco
On 10/16/06, Stefan Lindner <[EMAIL PROTECTED]> wrote:
When I deploy my wicket application with the current apache svn wicket build
the following occurs in the web container's logfile
DEPRECATED! Please use WicketFilter instead
My Application fails to load. The only place where this class appears in my
alpplication is in the web.xml file
<servlet-class>wicket.protocol.http.WicketServlet</servlet-class>
All examples in wicket-exampls has still this servlet-class. But if I replace
WicketServlet by WicketFilter
<servlet-class>wicket.protocol.http.WicketFilter</servlet-class>
My application trhows an exception during deploy
00:04:29,843 INFO [[/Visiomedic]] Marking servlet Visiomedic as
unavailable
00:04:29,859 ERROR [[/Visiomedic]] Servlet /Visiomedic threw load() exception
java.lang.ClassCastException: wicket.protocol.http.WicketFilter
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.
java:1055)
What's wrong?
