.gwt.xml
. Module XML files should reside in your
project's root package.
If you are using the standard project structure, your module XML can be as simple as this:
<module> <inherits name="com.google.gwt.user.User"/> <entry-point class="com.example.cal.client.CalendarApp"/> </module>
Modules are always referred to by their logical names. The logical name
of a module is of the form pkg1.pkg2.ModuleName
(although any number of packages may be present) and includes neither
the actual file system path nor the file extension. For example, the
logical name of a module XML file located at
~/src/com/example/cal/Calendar.gwt.xmlis
com.example.cal.Calendar
If no <source>
element at all is defined in a
module XML file but the directory containing the module XML contains a
subdirectory called client
, then the
client
subdirectory is added to the source path as if
<source path="client">
had been found in the XML.
This default helps keep module XML compact for standard project
layouts.
If no <public>
element at all is defined in a
module XML file but the directory containing the module XML contains a
subdirectory called public
, then the
public
subdirectory is added to the public path as if
<public path="public">
had been found in the XML.
This default helps keep module XML compact for standard project
layouts.
/spellcheck
).
Your client code then specifies this URL mapping in a call to
ServiceDefTarget.setServiceEntryPoint(String). Any number of
serlvets may be loaded in this manner, including those from inherited
modules.