handling static content

[Brill Pappin <br...@pappin.ca>]

I'm attempting to have wicket run from the base directory "filter mapping is
/*".
The trouble is that I have a lot of static content I don't want in the
classpath. i.e. I want it in the normal place content is located, in
src/main/webapp.
 
I've managed to modify the Path stripper example so that I can remove the
package names from the paths (for instance, images/x.gif) and its working
but now I think I'm actually forcing the filter to do a lot more work than
is really required because every request regardless of there being anything
to process.
 
How do others on this list handle static content?
 
- Brill Pappin
 

Re: handling static content

[Eelco Hillenius <ee...@gmail.com>]

On 10/28/07, Brill Pappin <br...@pappin.ca> wrote:
> I'm attempting to have wicket run from the base directory "filter mapping is
> /*".
> The trouble is that I have a lot of static content I don't want in the
> classpath. i.e. I want it in the normal place content is located, in
> src/main/webapp.

Just can just put those images in there. And use plain img tags. If
Wicket's filter can't handle certain content, the request will fall
through and the container (or whatever filter is defined next) will
handle it.


Eelco

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org