I've gone back to using a copy of InjectedHttpServlet from the previous snapshot, and am whole again with onyl a small amount of code.
I think the new servlet stuff is cool for people who are using servlets as a programming methodology. However, for people like me who aren't writing new servlets, merely using a servlet as an adapter between an existing system and something better (Restlet, in my case), it's too much engineering for too little benefit: - It makes it difficult for me to get the Injector for use by Tim Peirels' Restlet integration - There's no clear place to put the warm-up code that currently goes into myservlet.init, other than a series of eager singletons with sculpted dependencies. - Legacy app developers who look for my entry-point servlets in web.xml will be puzzled when they can't find anything. Personally, my preference would be to see the Guice servlet functionality split into two parts - one for bare support for injection of servlets (InjectedHTTPServlet, GuiceServletContextListener) - a second with the cool new dispatch, Request/Response/Session injection, and scopes. Leigh. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to google-guice@googlegroups.com To unsubscribe from this group, send email to google-guice+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-guice?hl=en -~----------~----~----~----~------~----~------~--~---
