Installation
These steps will quickly get JumpStart open, running, and editable. These steps are for v1.5.1 and v1.5.0.
- Unzip. Unzip the downloaded file, which will give you a directory called jumpstart-min-1.5.1 or similar.
- Get JBoss Application Server.
- Go to JBoss Application Server Downloads, locate 4.2.1 GA and choose the Download link. Choose to download the jboss-4.2.1.GA.zip.
- Once downloaded, unzip it. Move it to a suitable location (eg. /devel/jboss-4.2.1.GA).
- Move JumpStart to your development projects location. Move jumpstart-min-1.5.1/ or jumpstart-max-1.5.1/ to your development area, eg. /devel/jumpstart-min-1.5.1/ .
- Open it in Eclipse. Open Eclipse and create a new Java Project over the jumpstart-min-1.5.1/ or jumpstart-max-1.5.1/ directory. The project can't build just yet so it will show errors.
- Run the get-dependent-files target
in the project's build.xml file. You can do these steps in Eclipse...
- If you haven't used Ant in Eclipse before, start by opening the Ant view and dragging build.xml onto it.
- Open the build.properties file and modify the jboss.dir property.
- If your internet connection is through a proxy then
modify the setproxy tag in build.xml, eg.
<setproxy proxyhost="proxy.mycompany.com" proxyport="8080"></setproxy> - Run the get-dependent-files target in the project's build.xml file.
- web/src/main/webapp/WEB-INF/lib/
- enterprise/src/main/lib/
- business/src/main/lib-compile/
- business/src/test/lib-test/
- Refresh the project by right-clicking on the project in Eclipse and choosing Refresh. This should build the project successfully and show no errors. It will also run exploder.xml, which will build the exploded/ directory. You can see how has this been configured by displaying the project's properties ans choosing Builders.
- Point JBoss at the project.
Locate the server's conf/jboss-service.xml file
eg. jboss-4.0.5.GA/server/default/conf/jboss-service.xml.
Edit it, replacing this:
-
<attribute name="URLs">
deploy/
</attribute>-
<attribute name="URLs">
deploy/, /devel/jumpstart-min-1.5.1/exploded/
</attribute> - Start JBoss Start the JBoss server from the command line by going to JBoss's bin/ directory and using the run.bat or run.sh command.
- Check JumpStart is running by pointing your web browser at http://localhost:8080/jumpstart-min or http://localhost:8080/jumpstart-max, but don't expect to be able to log in yet.
- Load initial data:
- Open the Hypersonic Database Manager. To do this, point your web browser at http://localhost:8080/jmx-console/, click on database=localDB,service=Hypersonic, find the section labelled void startDatabaseManager() and click on Invoke. In a few moments a Java GUI called HSQL Database Manager will start up.
- In Eclipse, locate business/src/main/examples/setup/initial_data.sql in the project. Open it, then copy and paste its contents into the HSQL Database Manager and click on Execute SQL.
- Confirm JumpStart is working by returning to http://localhost:8080/jumpstart-min or http://localhost:8080/jumpstart-max and logging in with secofr for the Login ID and secofr for the Password.
- Finished! There are 2 other users: admin and john, with passwords admin and john, respectively. In Max, these users are authorised to less functions than secofr.
- Try making a mod! As another quick test...
- In Eclipse, locate the html template of the login page -
web/src/main/webapp/WEB-INF/pages/login/LoginPage.html
- and modify it a little.
Remember - you can immediately preview the mod by opening the html file with a web browser, or in Eclipse try Open With > Web Browser if that option is available. This is one of Tapestry's many strengths. - Make JBoss notice the change by running the Ant target called touch-exploded-ear in JumpStart's build.xml file. JBoss will automatically reload the app.
- In future you can avoid the need to reload - see Reloading...automatically on the Tips page.
- In Eclipse, locate the html template of the login page -
web/src/main/webapp/WEB-INF/pages/login/LoginPage.html
- and modify it a little.
- Explore! Visit the Orientation, Tips, Troubleshooting and Bugs & Enhancements pages for more info.