Hi all, Opinion on this thread seems pretty much one way, but I currently know little of Jetty.
1) Can anyone give a brief summary of why Jetty is "better" than Tomcat? 2) Can I be reassured I won't run into unforeseen difficulties deploying to JBoss? regards gregor On Oct 20, 2:03 pm, Alex <[EMAIL PROTECTED]> wrote: > Switching to jetty would be fine we me and my colleagues as well. We > use -noserver for hosted mode and unit testing (with some hackery). > > On Oct 13, 5:48 pm, "Bruce Johnson" <[EMAIL PROTECTED]> wrote: > > > Hi everyone, > > Hope you're enjoying 1.5. > > > The GWT team has started putting together a 1.6 roadmap, which we'll publish > > as soon as we have it nailed down. Two of the areas we want to work on for > > 1.6 are some improvements to hosted mode startup time and a friendlier > > output directory structure (something that looks more .war-like). > > > 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. > > > Thanks, > > Bruce --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
