You can make a simple wrapper that is HttpServlet, or ask Jersey to update to using Filters or HttpServlets. I made the case on JSR-311 that we should not be supporting non-HTTP servlets and this was accepted by everyone on the EG. So if anything I consider it a bug in Jersey's implementation.
Dhanji. On Sat, Feb 14, 2009 at 12:59 PM, 盛 宁 <[email protected]> wrote: > Cause Jersey's ServletContainer is implementing Servlet but not extending > HttpServlet. I wrote a filter to delegate it without success. > Rex > > On Feb 14, 2009, at 8:25 AM, Dhanji R. Prasanna wrote: > > This is because GuiceFilter is only intended to work in HttpServlet > environments. If there was a HttpFilter I would have used that instead (it's > quite a pain to downcast ServletRequest every time as it is). > IMO Servlet should be deprecated. > > Dhanji. > > On Sat, Feb 14, 2009 at 3:29 AM, Rex Sheng <[email protected]> wrote: > >> >> Hi, Dhanji, >> warp-servlet move to google-servlet, so, I post my question here: >> >> The FilterKeyBindingBuilder uses javax.servlet.Filter in 'through's, >> but why ServletKeyBindingBuilder uses javax.servlet.http.HttpServlet? >> >> I think it should be javax.servlet.Servlet cause web.xml will work on >> a javax.servlet.Servlet which not required to be HttpServlet. >> >> Thanks, >> Rex >> >> >> > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
