(GPE-Fork V2) GWT Super Dev Mode debugging with a Custom Web Server
This video covers debugging a GWT application with a custom web server using Super Development Mode. It uses a plain basic python web server as the basic web server. But any local, remote, docker apache web server, etc, could be used in debugging a GWT application. The two most important program arguments in debugging with a custom web server are: 1. -noserver 2. -war /path/to/output/war/directory This doesn't cover using the WTP server runtimes as the custom web servers. More can be found here: http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/servers/Servers.html Eclipse Server Runtime for Tomcat Server: http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/servers/Tomcat.html Eclipse Server Runtime for App Engine: http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/servers/AppEngine.html
This video covers debugging a GWT application with a custom web server using Super Development Mode. It uses a plain basic python web server as the basic web server. But any local, remote, docker apache web server, etc, could be used in debugging a GWT application. The two most important program arguments in debugging with a custom web server are: 1. -noserver 2. -war /path/to/output/war/directory This doesn't cover using the WTP server runtimes as the custom web servers. More can be found here: http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/servers/Servers.html Eclipse Server Runtime for Tomcat Server: http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/servers/Tomcat.html Eclipse Server Runtime for App Engine: http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/servers/AppEngine.html