commit 08171214dd185e00766d007c81e484c4e7cdeb38
author scottb@google.com <scottb@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Wed Oct 29 21:45:14 2008 +0000
committer scottb@google.com <scottb@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Wed Oct 29 21:45:14 2008 +0000
tree e95b3999ef954de3e583070aca1b5034f350e0d6
parent c14d368498d7183fa30fc2e73ba36f235cd1949b

Initial support for WAR deployment.  GWTCompiler happens to be backwards-compatible with the legacy format, but the behavior of the shell differs.  Therefore we created a new entry point, GWTHosted, which is the new GWTShell and runs with WAR assumptions.

Summary of WAR mode:
- Assumes output folder is in WAR format
- Runs Jetty; embeds GWTShellServletFilter to autogenerate modules on demand
- Uses true linking (and the new relinking); dumps resources and generated selection script directly into output folder
- Ignores the <servlet> tag; servlets must be initialized via WEB-INF/web.xml in the output folder

Summary of legacy mode:
- Same behavior as GWT 1.5
- Uses Tomcat (but we want to eventually replace with Jetty); uses GWTShellServlet
- Serves files directly from public path and work directory; uses the old HostedModeLinker to generate the selection script
- <servlet> tag still works

Additionally, a GWT module file now supports a "deploy-to" attribute at the top level, which allows the subdirectory within the output folder for a module to be overridden (the default is the fully-qualified module name).

Patch by: scottb, bruce, bobv (two-pair programming)
Review by: bobv, scottb


git-svn-id: https://google-web-toolkit.googlecode.com/svn/releases/1.6@3890 8db76d5a-ed1c-0410-87a9-c151d255dfc7