jetty or tomcat, no problem for us. But startup speed certainly is! we use -noserver with jboss/oc4j and weblogic.
Few thing I would like to propose/request in upcoming release: #1. Seamless hot deployment for any source code change(class signature as well as stmt changes). So when the user refreshes the browser, js compilation does not take place. it will just load whatever exists. Hot deployment will make sure that whatever exists is always current. I know this is difficult to achieve but if it is implemented, the development time will be super super fast. We will basically have to run the app in hosted mode browser only once. And all subsequent changes will be auto deployed(synched) with the hosted mode. In big applications like ours, almost every code change requires hosted mode refresh. And in most cases it takes any where between 50 to 200 secs. #2. If #1 is not possible: gwt should atleast detect the files that were changed since app was last refreshed and attempt to compile load only those changes. Some how the compiler/loader/linker should be smart enough to the level where hosted mode refresh is reduced to less than 7 seconds. Really looking forward towards a super fast hosted mode. Thanks, Rakesh Wagh On Oct 20, 9:46 am, John <[EMAIL PROTECTED]> wrote: > Manuel Carrasco wrote: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 > +1 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
