Well, I don't particularly find them useful. Most of the startup or shutdown logic can be encapsulated in the filter's (or servlet's) init() and destroy().
No one has made a compelling argument about why we should support ServletContextListeners. That is not to say there isn't one. Do you have a use case? Dhanji. On Tue, Mar 3, 2009 at 5:49 PM, Martin Lukasiewycz <[email protected]> wrote: > > Hi Dhanji, > is it on purpose that i can add only Filters and Servlets in a > ServletModule but not a ServletContextListener? > > Regards, > Martin > > On Mar 3, 3:29 am, "Dhanji R. Prasanna" <[email protected]> wrote: > > On Tue, Mar 3, 2009 at 9:53 AM, Jon Gorrono <[email protected]> > wrote: > > > > > Well, I am over the pain of my first let down, so it is up to you: > > > does a filter declaration requirement amount to a complete elimination > > > of web.xml from your web application? :) > > > > Note that in Servlet 3.0 containers you won't even need to do the filter > > decl. > - Show quoted text - > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
