Cafesolo wrote: > This is the exception's stack trace: > > java.lang.IllegalArgumentException: Error initializing WicketFilter - > you have no <filter-mapping> element with a url-pattern that uses > filter: Key[type=org.apache.wicket.protocol.http.WicketFilter, > annotation=[none]] > at org.apache.wicket.protocol.http.WicketFilter.getFilterPath > (WicketFilter.java:907) > at org.apache.wicket.protocol.http.WicketFilter.init > (WicketFilter.java:654)
Ah, thought it might be that - so, no, setting the name is not the important thing here at all. If you have a look at WicketFilter's sourcecode you can see that it's trying to figure out what the root path assigned to WicketFilter within your webapp is - and that the Wicket developers have provided a way for you to pass that via a filter configuration parameter if your setup is such that Wicket can't fish it out of web.xml itself. There does appear to be one small bug in WicketFilter though - the part where it tries to trap exceptions from determining the url-pattern doesn't catch IllegalArgumentException. Max.
signature.asc
Description: OpenPGP digital signature
