Friday, September 11, 2015

Problems GWT2.7 superdevmode + tomcat server

The general idea is:
* launch your app the same you'd normally do (for production), except you don't need to compile your GWT client code, and you have to serve static assets from a directory (i.e. not a packaged WAR but an "exploded" one, or if you're of an "self-contained executable jar" kind, not from the jar itself, yet possibly from the classpath anyway)
* launch SDM with launcherDir pointing to the directory served by the previous server, where it will create the (missing) *.nocache.js. It'll also copy resources from the "public path", but that's basically it.

You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment