| scottb@google.com | d1c2148 | 2009-02-18 00:26:01 +0000 | [diff] [blame] | 1 | <html> |
| 2 | <head> |
| 3 | <meta http-equiv="content-type" content="text/html; charset=UTF-8"> |
| 4 | <title>Servlet Mappings, GWT Modules, and web.xml</title> |
| 5 | </head> |
| 6 | <body> |
| 7 | |
| 8 | <p>GWT modules may declare one or more <code><servlet></code> |
| 9 | tags. These define Java Servlets that implement the server-side |
| 10 | component of a GWT-enabled web application.</p> |
| 11 | |
| 12 | <p>Prior to GWT 1.6, these GWT module servlet tags controlled the set of |
| 13 | servlets were actually instantiated during hosted mode. But as of GWT 1.6, this |
| 14 | is no longer true. Instead, the web application's <code>WEB-INF/web.xml</code> |
| 15 | configuration file controls what servlets are instantiated. A GWT module |
| 16 | specifies only what servlets are <i>expected</i>. |
| 17 | |
| 18 | <p>During hosted mode startup, the set of expected servlets (from GWT module |
| 19 | <code><servlet></code> tags) is validated against the set of actual |
| 20 | servlets (from the <code>WEB-INF/web.xml</code>) and a warning is issued for |
| 21 | each expected servlet which does not match an actual servlet. |
| 22 | |
| 23 | </body> |
| 24 | </html> |
