Running the Examples from Source

The process for running the the examples from source is quite simple. We have supplied an embedded application server (Jetty) which can be run directly from your IDE. Note that you are not obligated to use the embedded server; you can compile and deploy to any application server of your liking.

The steps for deploying and running the examples from the source distribution can be outlined as follows:

  • Download the distribution
  • Unpack the distribution to your workspace
  • Create the war archive
  • Deploy and run the examples
The following sections will elaborate these steps further.

Download the Distribution

In order to build the examples from the distribution you need to download the latest distribution from a mirror close to you. After the download you have to unpack the archive which will give you
  • a directory containing all necessary libraries
  • a directory containing all sources, including a Jetty configuration file
  • a directory containing some basic documentation.
  • an ant build file
  • a maven project file

Integrate into your Workspace

Copy this directory structure to your workspace and update your IDE to use this directory as a project. For instance, you could instruct the Eclipse 'New Java project' wizard to create a project in the directory of the Wicket examples. Let Eclipse figure out what the source directories are and which libraries are needed on the classpath. For other IDE's your milage may vary. Just make sure that you do the following:
  • add all jar files in the lib directory to the classpath
  • add the src/java directory as a source directory
  • compile the sources using your IDE, or using the supplied ant build file

Running the Examples

Try to find the wicket.examples.Start class in your IDE. This class has a main() method which starts the embedded server. Run this class. In Eclipse, you can just select the src/java directory, and select 'Run as -> Java application' in order to run the examples. The only thing you *really* need to take care of is making sure no other application server is using port 8080, otherwise the embedded application server is not able to start. If you are not able to stop the other application server, you might consider changing the port setting in the src/etc/jetty-config.xml file to another port number. Now the only thing left to do is pointing your browser to: 
					http://localhost:8080/wicket-examples