| Simple implementation of the Quartz Job interface, applying the
passed-in JobDataMap and also the SchedulerContext as bean property
values. This is appropriate because a new Job instance will be created
for each execution. JobDataMap entries will override SchedulerContext
entries with the same keys.
For example, let's assume that the JobDataMap contains a key
"myParam" with value "5": The Job implementation can then expose
a bean property "myParam" of type int to receive such a value,
i.e. a method "setMyParam(int)". This will also work for complex
types like business objects etc.
Note: The QuartzJobBean class itself only implements the standard
Quartz
org.quartz.Job interface. Let your subclass explicitly
implement the Quartz
org.quartz.StatefulJob interface to
mark your concrete job bean as stateful.
This version of QuartzJobBean requires Quartz 1.5 or higher,
due to the support for trigger-specific job data.
Note that as of Spring 2.0 and Quartz 1.5, the preferred way
to apply dependency injection to Job instances is via a JobFactory:
that is, to specify
SpringBeanJobFactory as Quartz JobFactory
(typically via
SchedulerFactoryBean.setJobFactory SchedulerFactoryBean's "jobFactory" property}).
This allows to implement dependency-injected Quartz Jobs without
a dependency on Spring base classes.
author:
Juergen Hoeller
since:
18.02.2004
See Also: org.quartz.JobExecutionContext.getMergedJobDataMap
See Also: org.quartz.Scheduler.getContext
See Also: JobDetailBean.setJobDataAsMap
See Also: SimpleTriggerBean.setJobDataAsMap
See Also: CronTriggerBean.setJobDataAsMap
See Also: SchedulerFactoryBean.setSchedulerContextAsMap
See Also: SpringBeanJobFactory
See Also: SchedulerFactoryBean.setJobFactory | 