it doesnt make much sense to map the same filter instance to two different paths...
-igor On Sat, Mar 5, 2011 at 5:16 AM, Juergen Donnerstag <juergen.donners...@gmail.com> wrote: > I don't know. May be too long ago. > > -Juergen > > On Fri, Mar 4, 2011 at 4:49 PM, Martin Grigorov <mgrigo...@apache.org> wrote: >> Hi, >> >> In the context of https://issues.apache.org/jira/browse/WICKET-3497 I want >> to ask other Wicket devs whether WicketFilter parses only one >> <filter-mapping> and ignores others by intention ? >> Debugging https://issues.apache.org/jira/browse/WICKET-3497 I think Wicket >> 1.4 handles the case with two or more <filter-mappings> on the same <filter> >> by accident. >> >> So my question is: were there any discussions (around Wicket 1.1/1.2) that >> WicketFilter/WicketServlet should work only with the first <**-mapping> ? >> >> >> Example from the ticket quickstart: >> >> <servlet> >> <servlet-name>wicket.getUrlTest</servlet-name> >> <servlet-class>org.apache.wicket.protocol.http.WicketServlet</servlet-class> >> <init-param> >> <param-name>applicationClassName</param-name> >> <param-value>fs.quick.wicket.WicketApplication</param-value> >> </init-param> >> </servlet> >> >> <servlet-mapping> >> <servlet-name>wicket.getUrlTest</servlet-name> >> <url-pattern>/app/*</url-pattern> >> </servlet-mapping> >> >> <servlet-mapping> >> <servlet-name>wicket.getUrlTest</servlet-name> >> <url-pattern>/longapp/*</url-pattern> >> </servlet-mapping> >> >> martin-g >> >
