This work is based upon the examples for the Wicket in Action Book written by Martijn Dashorst and Eelco Hillenius.
http://manning.com/dashorst/
http://code.google.com/p/wicketinaction/

It is primarily the same content, but just the pieces without the extra infrastructure that confuses things with
the downloadable examples.

This version integrates the CheckOut.html panel, the checkout logic, and it also moves one of the callbacks into its own 
class. I don't quite agree with having anonymous inner classes for callbacks. Say you have a callback used in more than one place. With 
an anonymous inner class, you are going to copy the callback to two places, contradictory to good programming practices. 


This project uses Maven. You of course need a java compiler too.
http://maven.apache.org

If you don't have Maven installed, install it. Then, to run the project, do
the following, under Windows or GNU/Linux. Don't type the '$' sign. That is to indicate the prompt.

Compile
$ mvn compile

Run it using Jetty. Point your browser to http://localhost:8080/giraffe/
$ mvn jetty:run

Create a war file. The resulting war file is in the target directory.
$ mvn package

If you are using Eclipse, you should have the Maven plugin installed. 
http://maven.apache.org/eclipse-plugin.html

Then, once you have it installed, you can import the project using the following menu selection
File->Import
Existing Projects into Workspace

The dependency jars should automatically populate. I haven't tried using it with other IDEs. If you
are not familiar with Maven, importing it will help understand the directory structure.

The file placement for this Wicket project is a bit wierd. The html files go in the same place as
the java files, yet the css and the png files go in the webapp directory. 

You will notice that this application doesn't show much as far as the front end, but it is loading
the application context and delivering the main page.  I consider it a good jump off point.

brian
--
Brian E. Lavender
http://www.brie.com/brian/

