1 |
3192
|
berkley
|
Author: Chad Berkley
|
2 |
|
|
Date: 3/5/2007
|
3 |
|
|
|
4 |
3195
|
berkley
|
This file covers deploying the gwt created ajax code and servlet to a non-google
|
5 |
|
|
version of tomcat. This allows for the installation of the servlet(s) along
|
6 |
|
|
side a normal metacat installation. This file assumes you've already done
|
7 |
|
|
the steps highlighted in the README file.
|
8 |
3192
|
berkley
|
|
9 |
3195
|
berkley
|
1) Create a servlet on your tomcat instance called "rpc". This is a simple
|
10 |
|
|
servlet that just runs the google remote procedure call (rpc) services. Use
|
11 |
|
|
the web.xml file from the ./tomcat/webapps/ROOT/WEB-INF directory. You'll
|
12 |
|
|
also need to copy all of the gwt jar files from your gwt installation as well
|
13 |
|
|
as all of the jar files in ./lib. Use the gwt-user.jar and gwt-dev.jar from
|
14 |
|
|
metacat/lib. If you use the ones from the gwt distro, tomcat won't load them
|
15 |
|
|
due to the presence of javax.servlet.Servlet.
|
16 |
3192
|
berkley
|
|
17 |
3195
|
berkley
|
2) copy ./src/org/kepler/web/service/KeplerServiceServlet.java to
|
18 |
|
|
metacat/src/org/kepler/web/service/ and update the KeplerServiceServlet.java
|
19 |
|
|
Edit the file with the correct url to your metacat servlet (line 6 in the code).
|
20 |
|
|
Make sure the moduleRelativeURL exactly matches the url that will be browsed
|
21 |
|
|
to! I.E. Don't use "localhost" if you intend to browse to an actual machine
|
22 |
|
|
name. This confuses the RPC and will cause problems.
|
23 |
3192
|
berkley
|
|
24 |
3195
|
berkley
|
3) run 'ant package' (from the ajax dir) and copy the newly created
|
25 |
|
|
kepler-web.jar file to metacat/lib/. Make sure you updated the hard coded
|
26 |
|
|
servlet paths in the java code before doing this.
|
27 |
3192
|
berkley
|
|
28 |
|
|
4) run 'ant install' from your metacat directory
|
29 |
|
|
|
30 |
|
|
5) make sure tomcat restarts
|
31 |
|
|
|
32 |
3195
|
berkley
|
6) run ./KeplerClient-compile and copy the contents of the www directory
|
33 |
|
|
to some web accessible location, then browse to the KeplerClient.html file
|
34 |
|
|
and the javascript should run.
|
35 |
3192
|
berkley
|
|
36 |
|
|
--------------------------------
|
37 |
3195
|
berkley
|
If this doesn't work for some reason, keep in mind the main things you need.
|
38 |
|
|
They are:
|
39 |
3192
|
berkley
|
* the rpc servlet
|
40 |
3195
|
berkley
|
* the KeplerServiceServlet servlet. In the web.xml file, I have called this
|
41 |
|
|
'gwt' so the address will be: http://server:8080/servletpath/gwt
|
42 |
|
|
* the compiled javascript (ajax) code
|
43 |
3192
|
berkley
|
* hard coded server/servlet paths correctly changed
|
44 |
|
|
* all jar files accessible to tomcat
|