using a filter has certain advantage, which are all outlined in the discussion thread on this list we had when deciding to switch to the filter. just search the archives.
this sounds like a bug in tomcat, why dont you take it to their list? the way that jetty works is that it installs a default catch-all servlet in order for filters to run at all, so you might have to do the same thing. -igor On Sun, Oct 26, 2008 at 2:26 AM, Roberto Fasciolo <[EMAIL PROTECTED]> wrote: > > Hi, > > I was profiling my application running on tomcat and I've found out that a > lot of CPU time is spent in ProxyDirContext.lookup(String). After > investigating the tomcat source code I've found that that method is invoked > when tomcat is trying to figure out what it should invoke basing on the > received URL. > > Our application has the WicketFilter mapped to /* and no servlet defined, so > my guess is that tomcat finds immediately the filter but then it tries to > look for a servlet matching the required page's URL. > > Based on the wiki in wicket 1.3 the recommended way of mapping it is by > using the filter instead of the servlet, but what's the drawback of using > the servlet (if being careful with mappings so that static contents are > served by tomcat)? > > Thanks in advance, > -Roberto > -- > View this message in context: > http://www.nabble.com/Problem-with-using-wicket-as-a-filter-tp20171597p20171597.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
