Now that you've generated your object model with Torque, and created a sample application, you are now ready to compile everything. Again, Maven is used to control the build process.

First, we need to tell maven where the java source files are located. To do this, add the following section just after the <dependencies> of your project.xml which you created sooner on in the top level directory of your project:

Afterwards, you can compile your jave source files by typing the following in the top-level directory of your project:

If you've done everything correctly, this should build without any errors. All of the resulting Java class files are placed in the target/classes directory. If the compiler misses any external libraries, review the <dependencies> section in your project.xml. Should you encounter other errors, go back and review your application code.

Before you run the sample application, you must first set your classpath (this was done automatically for you by Maven when you compiled). The classpath must include: all of the jars denoted in the <dependencies> section of your project.xml, and all of your application and object model classes located in target/classes.

Before compiling your application, maven will have downloaded all libraries your project depends on to the local maven repository. Gathering them from there is a cumbersome process. To ease copying them into one place, we modify Maven's build process a little. For this, you need to create a new file called maven.xml in the top-level directory of your project. It needs to have the following content:

After creating the file, re-run

Now change into the target directory. In addition to the classes subdirectory which was already created in the first compilation run, you see that maven has generated an additional lib directory which contains the needed libraries, and that maven also copied the Torque.properties file here.

Now everything is in one place, and you can start the application by typing (note:exchange the mysql-connector-java-5.0.4.jar by the datatbase driver jar you are using)

If all goes well, you should see the following output:

If your application throws an exception, it could be for one of many reasons, most of which are not very descriptive unfortunately. Do not be discouraged if your application does not run the first time. Carefully retrace all of the steps outlined in this tutorial. If you are still not able to get your application to run, use the Torque user mailing list to your advantage.