> 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.
That all said, I almost never use Hosted Mode, and system admins don't have to
deal with a development time engine. Tomcat does have much better IDE support
than Jetty, but since Hosted Mode is in charge of that, again it makes no real
difference. When I do run Hosted Mode it's with the -noserver option.
So my end opinion: I think the change is a good idea, since the additional speed
and lower memory load will encourage people trying out GWT for the first time.
Hi, this is pretty nice widget. For those who is puzzled by the demo not working in Firefox. I would suggest you to download the latest source code and run it locally. The ScrollTable works nicely in both Firefox/Chrome & IE.
One question though, will column drag and drop be supported in the future?
Please can someone update the docs and example. This is a brilliant widget but in this state its almost unusable :(
Since complicated configurations aren't really something you want to
address in the embedded server, my vote would be for the simplest,
fastest implementation that supports the simple case uses.
So, if Jetty starts faster and is lighter weight, then great, use it.
My project requires a full blown JEE container, not just a servlet
engine, so neither tomcat nor jetty would be enough. I have been using
-noserver since the beginning and it works great.
If the embedded server doesn't fit your needs (no matter what that
server ends up being) then it is no big deal to use whatever server
does work for you.
The most annoying issue with GWT is performance in development mode. I mean, compiling, startng hosted mode and running GWT Unit tests. So any action that improves these is welcome.
So my vote if for jetty