I'm definitely interested in getting simple servlets to run in Super Dev Mode in a way similar to classic Dev Mode. I haven't investigated, so I don't know if it's better to reuse the existing implementation or write a fresh one and leave behind some crud.
I don't think we want to try too hard to provide a servlet container that works for arbitrary web apps. Typically it's better to use a separate process for anything complicated and avoid classpath/class loader issues. For example, for App Engine, you'll want to be using its own dev_appserver command. But perhaps I'm biased by how we do things within Google? - Brian On Fri, Jun 8, 2012 at 1:38 AM, Thomas Broyer <[email protected]> wrote: > 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
