Google Web Toolkit integration


Getting Started

Each resource type can have its own GWT code, e.g.the policy manager resource type


One can build the GWT source by running the gwt:compile ant target, e.g.

./ -f src/resources/policymanager/build.xml gwt:compile

whereas please make sure that the resource type build file imports the file instead the regular file

The gwt:compile target compiles the GWT Java code to cross-browser Javascript code and saves it within the htdocs directory of the corresponding resource type, e.g.


Configuration of GWT version

The GWT version can be configured per resource type within src/build/, e.g.


Speeding up development

By default the GWT source is compiled for all GWT-supported browsers. While developing this can be overridden per resource type within the module configuration (property user.agent), e.g.


There are also some more flags within src/build/resource-types/ which can be set and help speeding up development, such as for example the -draftCompile fiag, but please be aware that these flags depend on the GWT version you are using (see above: Configuration of GWT version).

Each src-gwt directory can contain an optional build properties file, e.g.


containing the module names, e.g.

which helps to speed up development, because only this specific module will be compiled. But one can have several modules per src-gwt (*.gwt.xml) directory and if one wants to compile all at once, then one should remove such files.


Your comments are much appreciated

Is the content of this page unclear or you think it could be improved? Please add a comment and we will try to improve it accordingly.