CS 160

Homework 2

First draft due date: September 25

Second draft due date: October 1

Final version due date: October 9

Note: Homework assignments are individual work, even when they relate to the project. You may discuss your assignments with each other, but the work must be yours alone.

Problem #1. Start with QuickieQuiz from Lab 5.

You may not change any of the entity beans in your solution. (I will run the solution from my database, filled with my sample data.)

Problem #2. Prepare a progress report that describes your activities, using the same format as in assignment 1.

Problem #3. The QuickieQuiz zip includes a file build2.xml in the root of the project. (NetBeans uses its own build.xml, and we don't want to mess with that.) Implement the following feature into build2.xml: Add an Ant target run that launches the browser with your application. Find out how to launch the browser from Ant, and make sure your task has the appropriate dependencies. Make run your default target.

Submission instructions

Your solution will consist of a file report.html in the root directory of your project, and and all source files for the program, in the same layout as the QuickieQuiz project.

You will check your solution into your individual CVS sandbox. I will check out your work with the following commands:

export CVS_RSH=/usr/bin/ssh
export CVSROOT=:ext:username@oslo.cs.sjsu.edu:/home/cvsroot/sandbox/username
mkdir -p ~/gradehw2/username
cd ~/gradehw2/username
cvs checkout hw2
cd hw2
cp ~/build2.properties build.properties
ant -f build2.xml

My build2.properties contains these two lines.

glassfish.dir=/usr/local/glassfish
browser=/usr/bin/firefox

Yours should contain exactly two lines with the same keys and values that work for your system. Note that your file will be overwritten during testing.

You will want to try this yourself. (In the first checkin, I will manually point my browser to http://localhost:8080/QuickieQuiz-war.)

You will make at least three checkins at the dates given above. The second checkin must contain a solution to problem #3. Each checkin must contain an up-to-date report.html and a working (but not necessarily feature-complete) program. You are, of course, encouraged to frequently check in intermediate working versions.