Along with the coding of your application in an IDE, the GWT calls this development stage host mode. Figure 5 shows a GWT application running in host mode.
Here is what the GwtAjax-shell script or XXX-shell looks like:
#!/bin/sh APPDIR='dirname $0'; java -XstartOnFirstThread -cp "$APPDIR/src:$APPDIR/bin:/Users/bruceperry/1gwt/gwt-mac- 1.2.11/gwt-user.jar:/Users/bruceperry/1gwt/gwt-mac-1.2.11/gwt-dev-mac.jar" com.google.gwt.dev.GWTShell -out "$APPDIR/www" "$@" com.parkerriver.gwt.intro.GwtAjax/GwtAjax.html;
Notice the Java classpath, the quoted string following the -cp option in the shell script. It includes the /src and /bin directories in the top level of the application, as well as the gwt-user.jar and gwt-dev-mac.jar (or, for instance, gwt-dev-linux.jar) libraries.
The code that you use or depend on to create your application, before launching host mode, must be included on the classpath. For instance, if you are using various JAR files, such as jdom.jar, junit.jar, or log4j.jar (representing the JDOM XML-handling library, the JUnit unit-testing framework, and the log4j logging classes, respectively) to develop server-side classes, and these classes are a part of the GWT application, then include the appropriate JARs in this shell script's classpath.
Figure 7-1. A GWT application running within the framework's special browser