Packaging the Quartz Application

Let's finish off this early chapter by briefly discussing the process of packaging an application that utilizes the Quartz framework.

Quartz Third-Party Dependencies

Starting with the 1.5 distribution, you will see a lib directory. Underneath this directory, you'll find several subdirectories:

  • libcore
  • liboptional
  • libuild

For deployment, you absolutely need the Quartz JAR file, as well as some of the other dependent libraries. Which third-party libraries are required is somewhat dependent on whether you are running in a stand-alone environment or as part of a J2EE distribution. Typically, the Jakarta Commons libraries (commons-logging, commons-beanutils, and so on) are needed regardless. However, when deploying into an application server environment, you need to be sure not to copy JARs that are already present; if you do, you will generally get very strange results.

Table 3.1 lists the included third-party libraries and information to help you decide whether you need to include them.

Table 3.1. Quartz Third-Party Libraries Required/Optional



Where to Find More Information


Primarily used by JavaMail






Yes, if using a database for job storage



If you are using some of the plug-ins, you'll need it.





Sending e-mails


Yes, if using a database for job storage


Yes, if using a for job storage



Core Quartz Framework


If using a Servlet container, but it should already be present


Come on, who is not using this?


Configuration and Properties Files

You also must include with your application. If you are deploying your application in an exploded format, you should place the file in a directory that is loaded by the classloader. (An "exploded" format is one that is not contained within a JAR, WAR, EAR, or other Java archive, but that is laid on the file system in individual files.) For example, if you have a classes directory (such as a Web application's WEB-INF/classes directory), store the file there. If you are deploying in one of Java's archived formats, put the properties file in the root of the archive file. This same rule applies when using the quartz_jobs.xml file.

Scheduling in the Enterprise

Getting Started with Quartz

Hello, Quartz

Scheduling Jobs

Cron Triggers and More

JobStores and Persistence

Implementing Quartz Listeners

Using Quartz Plug-Ins

Using Quartz Remotely

Using Quartz with J2EE

Clustering Quartz

Quartz Cookbook

Quartz and Web Applications

Using Quartz with Workflow

Appendix A. Quartz Configuration Reference

Quartz Job Scheduling Framework(c) Building Open Source Enterprise Applications
Quartz Job Scheduling Framework: Building Open Source Enterprise Applications
ISBN: 0131886703
EAN: 2147483647
Year: N/A
Pages: 148 © 2008-2020.
If you may any questions please contact us: