Revision 3207
Added by berkley over 17 years ago
lib/ajax/INSTALL | ||
---|---|---|
19 | 19 |
Edit the file with the correct url to your metacat servlet (line 6 in the code). |
20 | 20 |
Make sure the moduleRelativeURL exactly matches the url that will be browsed |
21 | 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. |
|
22 |
name. This confuses the RPC and will cause problems.
|
|
23 | 23 |
|
24 |
3) run 'ant package' (from the ajax dir) and copy the newly created |
|
24 |
3) Copy the lib/gwt-*.jar files to metacat/lib. Note this may cause some |
|
25 |
problems with jsp compilation. |
|
26 |
|
|
27 |
4) run 'ant package' (from the ajax dir) and copy the newly created |
|
25 | 28 |
kepler-web.jar file to metacat/lib/. Make sure you updated the hard coded |
26 | 29 |
servlet paths in the java code before doing this. |
27 | 30 |
|
28 |
4) run 'ant install' from your metacat directory
|
|
31 |
5) run 'ant install' from your metacat directory
|
|
29 | 32 |
|
30 |
5) make sure tomcat restarts
|
|
33 |
6) make sure tomcat restarts
|
|
31 | 34 |
|
32 |
6) run ./KeplerClient-compile and copy the contents of the www directory
|
|
35 |
7) run ./KeplerClient-compile and copy the contents of the www directory
|
|
33 | 36 |
to some web accessible location, then browse to the KeplerClient.html file |
34 | 37 |
and the javascript should run. |
35 | 38 |
|
lib/ajax/KeplerClient-compile | ||
---|---|---|
1 | 1 |
#!/bin/sh |
2 | 2 |
|
3 | 3 |
APPDIR=`dirname $0`; |
4 |
GWT=/home/berkley/library.kepler-project/gwt
|
|
4 |
GWT=/home/berkley/tools/gwt
|
|
5 | 5 |
CLASSPATH="$APPDIR/src:$APPDIR/bin:$GWT/gwt-user.jar:$GWT/gwt-dev.jar:$APPDIR/lib/client.jar:$APPDIR/lib/utilities.jar:$APPDIR/lib/xalan.jar:$APPDIR/lib/xml-apis.jar" |
6 | 6 |
|
7 | 7 |
java -cp $CLASSPATH com.google.gwt.dev.GWTCompiler -out "$APPDIR/www" "$@" org.kepler.web.KeplerClient ; |
lib/ajax/src/org/kepler/web/client/MetacatResultsWidget.java | ||
---|---|---|
47 | 47 |
// Use a module-relative URLs to ensure that this client code can find |
48 | 48 |
// its way home, even when the URL changes (as might happen when you |
49 | 49 |
// deploy this as a webapp under an external servlet container). |
50 |
String moduleRelativeURL = GWT.getModuleBaseURL() + "kepler"; |
|
51 |
moduleRelativeURL = "http://library.kepler-project.org/kepler/gwt"; |
|
50 |
|
|
51 |
//String moduleRelativeURL = GWT.getModuleBaseURL() + "kepler"; |
|
52 |
//String moduleRelativeURL = "http://library.kepler-project.org/kepler/gwt"; |
|
53 |
//String moduleRelativeURL = "http://offhegoes.kicks-ass.net:8080/kepler/gwt"; |
|
54 |
String moduleRelativeURL = "http://library.kepler-project.org/kepler/gwt"; |
|
55 |
System.out.println("connection url: " + moduleRelativeURL); |
|
52 | 56 |
target.setServiceEntryPoint(moduleRelativeURL); |
53 | 57 |
} |
54 | 58 |
|
Also available in: Unified diff
updated installation instructions