I wonder if we shouldn't rather aim at integrating the ServletContainerLauncher with SuperDevMode; which could also be seen as: building a DevMode where the "code server" (the part to which the DevMode browser plugin connects, and runs your client code in the JVM) would be replaced by SuperDevMode.
That way, even if you have server-side code, you could launch a single Java app: SuperDevMode, instead of DevMode, that would embed 2 Web servers: a small Jetty for SuperDevMode, and the ServletContainer controlled by a ServletContainerLauncher (JettyLauncher by default) serving the -war folder as a standard webapp. That would also probably help in integrating SuperDevMode into Eclipse (remoteui), and eventually phase out DevMode (the one using browser plugins). What do you think? -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
