This page last changed on Jun 10, 2004 by ctran.

The following class performs the glue between Quartz and Webwork:

package com.trantek.sit.action;

import com.opensymphony.xwork.ActionProxy;
import com.opensymphony.xwork.ActionProxyFactory;
import org.quartz.Job;
import org.quartz.JobExecutionContext;
import org.quartz.JobExecutionException;

public class WebWorkJob implements Job
    public void execute(JobExecutionContext context) throws JobExecutionException
            ActionProxy proxy = ActionProxyFactory.getFactory().
                    createActionProxy("", context.getJobDetail().getName(), context.getJobDetail().getJobDataMap());

        catch (Exception e)
            throw new JobExecutionException(e);

To schedule webwork actions you simply create a job where

  • the name of your job is the name of the WW action to execute (no ".action" suffix).
  • all the parameters you want to send to the WW action is contained in the JobDataMap of the JobDetail

(the Quartz scheduler is setup as a servlet according to the javadocs of

The following code schedules an e-mail action:
Scheduler scheduler = StdSchedulerFactory.getDefaultScheduler();

JobDetail jobDetail = new JobDetail("email.send", 
                                     scheduler.DEFAULT_GROUP, WebworkJob.class);

Map m = jobDetail.getJobDataMap();
m.put("to", "");
m.put("subject", "quartz test");
m.put("body", "This is a quartz test, Hey ho");
m.put("smtpServer", "");
m.put("from", "");

SimpleTrigger trigger = new SimpleTrigger("myTrigger", 
                                          new Date(), null, 0, 0L);

scheduler.deleteJob("email.send", scheduler.DEFAULT_GROUP);
scheduler.scheduleJob(jobDetail, trigger);

This example is based on WW1:Integrating Webwork and Quartz

Document generated by Confluence on Dec 14, 2004 16:36