A final comment from Chris. I have now tied it in with a JavaDB which starts up on the fly. Obvious modifications would need to be made (such as introducing a connection pool or a singleton pattern or something like that) but basically the App now starts and does the following:
0 - Compile your GWT application. I've used the default Google GWT application that comes with the Eclipse plugin and hacked it around to make a call to the JSword API
1 - The user starts the application
2 - If the ESV (parameterizable) is not installed, it is downloaded from the internet from Crosswire. This step I'm sure we could try and bypass by distributing the bibles from Crosswire? Is that right Troy? as in distribute them as part of the installation disk (or at least one or two)
3 - The Jetty web server is started up (in process - invisible to the user)
4 - The Jetty web server is told to point at the compiled GWT application
5 - The user makes a request to http://localhost:8080 (in my case 8080 because that's what I've told Jetty to listen on).
6 - The Jetty server serves the first page (platform-targetted javascript and html) which prompts the user for his name
7 - When entered, a response is sent to the Jetty server and the GWT server side code kicks in. It used to send the name the user entered on the screen. Now however, it connects to JSword and sends Genesis 1:1 back to the user.
8 - It also displays the count of a table stored in the address table stored in JavaDB.
Java 1.6 makes sense...
Chris
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment