...
To avoid this issue with Wicket 1.3, the recommandation has been changed to use a ServletFilter rather than a servlet - See the Migrate-1.3 page for details of the changes required.
Wicket 2.x
To avoid this issue with Wicket 2.0, the recommandation has been changed to use a ServletFilter rather than a servlet - See the Migrate-2.0 page for details of the changes required.
More info
(Thanks, Igor)
Usually static resources are handled by the application server. The server knows it is serving a file and thus sets the last modified date of the resource to the last modified date of a file.
...
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.
For 1.3 & 2.xand onward, what we do is instead of using a servlet, use a filter.
...