...
What happens is that when a request comes in for /myapp/images/foo.gif
it will match the wicket servlet - so now it is wicket servlet's job to serve this file to the browser. now we are nice enough to provide support for this - but obviously we cannot do as good a job as the application server which has a lot more context.
So for 1.1 & & 1.2, we recommend mapping the servlet to something like /app/*
so that foo.gif
will be processed by the application server and only wicket-specific requests are processed by the servlet.
...