Yea, wicket does all this extra checking to baby sit your config. I'll talk to Eelco and see what the best way to make it work with Guice is. Dhanji.
On Sun, Aug 23, 2009 at 3:06 AM, Cafesolo <[email protected]> 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) > at com.google.inject.servlet.FilterDefinition.init > (FilterDefinition.java:81) > at com.google.inject.servlet.ManagedFilterPipeline.initPipeline > (ManagedFilterPipeline.java:102) > at com.google.inject.servlet.GuiceFilter.init(GuiceFilter.java:168) > at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java: > 99) > at org.mortbay.component.AbstractLifeCycle.start > (AbstractLifeCycle.java:40) > at org.mortbay.jetty.servlet.ServletHandler.initialize > (ServletHandler.java:589) > at org.mortbay.jetty.servlet.Context.startContext(Context.java:139) > at org.mortbay.jetty.webapp.WebAppContext.startContext > (WebAppContext.java:1218) > at org.mortbay.jetty.handler.ContextHandler.doStart > (ContextHandler.java:500) > at > org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java: > 448) > at org.mortbay.component.AbstractLifeCycle.start > (AbstractLifeCycle.java:40) > at org.mortbay.jetty.handler.HandlerWrapper.doStart > (HandlerWrapper.java:117) > at org.mortbay.component.AbstractLifeCycle.start > (AbstractLifeCycle.java:40) > at org.mortbay.jetty.handler.HandlerWrapper.doStart > (HandlerWrapper.java:117) > at org.mortbay.jetty.Server.doStart(Server.java:217) > at org.mortbay.component.AbstractLifeCycle.start > (AbstractLifeCycle.java:40) > ... > ... > > Regards, > -- Cafesolo > > On Aug 22, 12:46 pm, Brian Pontarelli <[email protected]> wrote: > > Send the exception. I doubt you need a name because that is primarily > > used to map a filter to a filter-mapping in the web.xml and serves > > little purpose beyond that. I'd be really surprised if Wicket was > > using this information. > > > > -bp > > > > On Aug 22, 2009, at 9:35 AM, Cafesolo wrote: > > > > > > > > > > > > > Hi Max, > > > > > In Wicket 1.4, the WicketFilter throws an exception if I configure it > > > using Guice instead of web.xml. > > > > > I think they made WicketFilter throw an exception if you don't specify > > > a name because you need a <filter-mapping> in your web.xml file, which > > > needs a <filter-name>...</filter-name> element. Correct me if I'm > > > wrong, but a filter without a mapping is useless, so I think they > > > wanted to throw a descriptive exception to make newbies lifes easier. > > > > > Regards, > > > -- Cafesolo > > > > > On Aug 22, 9:15 am, Max Bowsher <[email protected]> wrote: > > >> Cafesolo wrote: > > >>> Hi Dhanji, > > > > >>> I don't know why it needs a name. It's a Wicket thing. I'm sure > > >>> there > > >>> must be a good reason for this. > > > > >> Are you sure it really does? I use Wicket, though not (yet) with > > >> Guice, > > >> and I can't think of any particular reason. > > > > >> Max. > > > > >> signature.asc > > >> < 1KViewDownload > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-guice?hl=en -~----------~----~----~----~------~----~------~--~---
