I'm trying to build my first real app using wicket and am looking for advice on how to structure it. I expect it will have moderately heavy traffic but most things can be cached with a simple ehcache Filter.
The issue i see is that if i want to have wicket generated content on the root page, i need to map the application servlet to:
<url-pattern>/*</url-pattern>
But if i do that, it looks like all the static content has to go through wicket too. Is there any way to have the web server directly serve content under: /static/*?
Alternatively i guess i could map multiple application to deeper paths, but that seems like a bad idea.
I've read that 2.0 will switch to a filter model, what is the best practice until then?
thanks
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
