ml PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
Individual units of GWT configuration are XML files called modules
A module bundles together all the configuration settings that your GWT
project needs, namely
- Inherited modules
- An entry point application class name; these are optional, although
any module referred to in HTML must have at least one entry-point class
- Source path entries
- Public path entries
- Deferred binding rules, including property providers and class
Modules may appear in any package in your classpath, although it is
strongly recommended that they appear in the root package of a
standard project layout
A module entry-point is any class that is assignable to
and that can be constructed
without parameters. When a module is loaded, every entry point class is
instantiated and its
Modules can specify which subpackages contain translatable source
causing the named package and its subpackages to be added to the
. Only files found on the source path are candidates
in the same classpath without conflict.
When module inherit other modules, their source paths are combined so
that each module will have access to the translatable source it requires.
Modules can specify which subpackages are public
, causing the
named package and its subpackages to be added to the public path
be found on your public path are copied to the module's output directory.
The net effect is that user-visible URLs need not include a full package
When module inherit other modules, their public paths are combined so
that each module will have access to the static resources it expects.