jetty is awesome. In their latest drop (6.1.12.rc2 and rc3) there is a new feature in maven-jetty-plugin to reload jetty on keyboard events in console rather than automatically - it's indispensable when java GWT code lives in the same source tree as the server side java code (just in different package). And generally, maven jetty plugin is way better than Cargo stuff that's used for Tomcat.
Also, Jetty Continuations are just some much easier to work with than Tomcat's Comet. No wonder they are including it into Servlet spec 3.0. Nothing particularly wrong with Tomcat but I think it's just lagging in terms of developer productivity features behind Jetty. On Oct 13, 9:42 pm, "Michael Vogt" <[EMAIL PROTECTED]> wrote: > Hi Bruce. > > > As part of this effort, we've all but decided to switch the hosted mode > > embedded HTTP server from Tomcat to Jetty. Would this break you? (And if so, > > how mad would you be if we did it anyway?) We figure most people who really > > care about the web.xml and so on are already using "-noserver" to have full > > control over their server config. > > I personally would welcome Jetty. I'm using it as part of Grails right > now. It's fast and easy going. > > Cheers, > Michael --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
