|
1
|
Author: Chad Berkley
|
|
2
|
Date: 3/5/2007
|
|
3
|
|
|
4
|
Setup
|
|
5
|
-----
|
|
6
|
1) Make sure you have the google web toolkit installed. You can get it from
|
|
7
|
http://code.google.com/webtoolkit/. From now on, I will refer to the google
|
|
8
|
web toolkit directory as the "gwt" directory.
|
|
9
|
2) Make a symbolic link in the gwt directory so that
|
|
10
|
gwt-dev.jar -> gwt-dev-xxx.jar where xxx is either "mac", "linux" or "windows".
|
|
11
|
This just makes the scripting easier to deal with.
|
|
12
|
3) Edit the KeplerClient-shell file and make sure $GWT points to your
|
|
13
|
gwt installation. Do the same for KeplerClient-compile
|
|
14
|
|
|
15
|
Building
|
|
16
|
--------
|
|
17
|
Run the KeplerClient-shell script. Upon successful compilation, you should
|
|
18
|
see two windows open. One is the tomcat server shell, the other is a test
|
|
19
|
browser where you will see the web page.
|
|
20
|
|
|
21
|
Testing
|
|
22
|
-------
|
|
23
|
You can use the -shell file for incremental building and testing. If you want
|
|
24
|
to "clean" the project, you can use the ant build.xml file. The build file
|
|
25
|
really is not needed.
|
|
26
|
|
|
27
|
Installation/Deployment
|
|
28
|
-----------------------
|
|
29
|
Once you have a working product and you want to deploy to a normal instance
|
|
30
|
of Tomcat, you can first test that your code works under a normal browser by
|
|
31
|
clicking the "compile/test" button on the google browser. This will open your
|
|
32
|
page in whatever your default browswer is. Your server side code is still
|
|
33
|
running on the google tomcat instance (port 8888). If you want to deploy the
|
|
34
|
servlet and client side code to another instance of Tomcat, follow the
|
|
35
|
instructions in the INSTALL file.
|
|
36
|
|
|
37
|
A note on using different OSs
|
|
38
|
-----------------------------
|
|
39
|
There are a few differences when moving between windows, linux and osx.
|
|
40
|
On OSX, the -XstartOnFirstThread flag must be set in the KeplerClient-shell
|
|
41
|
and KeplerClient-compile scripts. Also, make sure you make a symlink for the
|
|
42
|
gwt-dev jar file. For some reason, google renames this jar depending on what
|
|
43
|
system you download gwt for.
|