* James Carnegie: > > I don't know the answer to your problem, but I am experiencing it too > and would be very interested in learning about any solutions you find. > > Customers need to be able to specify what URL's look like, so the Wicket > framework should _not_ dictate this. > > Can someone explain why we cannot use the <url-pattern>/*</url-pattern> > and have static resources loaded properly (with correct headers etc)?
You can try that: <servlet-mapping> <servlet-name>default</servlet-name> <url-pattern>*.css</url-pattern> </servlet-mapping> -- Jean-Baptiste Quenot aka John Banana Qwerty http://caraldi.com/jbq/ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user