Hi All, I'm working in 1.3.0 snapshot. Two or three weeks ago it used to be possible to use a filter-mapping like this one:
<filter-mapping> <filter-name>my.wicket.filter</filter-name> <servlet-name>my.servlet</servlet-name> </filter-mapping> But it looks like a recent change to getFilterPath now forces you to use url-mapping instead. This was encouraged before in all the documentation, but not explicitly enforced. The exception I'm seeing is at line 467 in WicketFilter. I know it may seem pointless to have a servlet consumer at the end of the wicket filter chain, but not allowing us to do it feels like an unnecessary limitation, and given the codebase I'm working within (Sakai) -- my initial guess is that it's going to represent a serious hurdle to making use of Wicket. So I guess I'm wondering if there's any chance getFilterPath could be massaged to allow servlet-name as well? Thanks, James. -- James Renfro [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user