Jens beat me to the reply, so I'll just answer one of the questions: how to update the app when either client side or server side code changes > are made. Joe says to cycle tomcat...what does that mean?
Just CNTRL-C to kill the tomcat and then run *mvn tomcat7:run-war* to recompile and redeploy it If you've just made server s I'm constantly going to the real code to figure out what has to change and then manually finding those same classes in Chromide changes, like modifying a backend service, then Maven will detect those changes and only recompile the backend Java. GWT will not recompile. On my dev machine, this means I can have the whole server recompiled and redeployed in about 15s. There are other more advanced code-hot swapping tricks you can do to a running tomcat, but I've only tinkered with those. I'm constantly going to the real code to figure out what has to change and > then manually finding those same classes in Chrome It would be great to have an ability to drill from a Chrome JS debugger line into the source file in an IDE. Since Chrome already has the FQDN and line number, it would not be that complicated to do with a hook into the IDE. Sounds like a missing Chrome Extension, the sort of thing the IntelliJ boys would build if people made enough noise. Sincerely, Joseph -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
