java.lang.Objectorg.quartz.JobDetail
org.springframework.scheduling.quartz.JobDetailBean
All Implemented Interfaces:
ApplicationContextAware, BeanNameAware, InitializingBean
JobDetail itself is already a JavaBean but lacks
sensible defaults. This class uses the Spring bean name as job name,
and the Quartz default group ("DEFAULT") as job group if not specified.
Juergen - Hoeller18.02.2004 - | Method from org.springframework.scheduling.quartz.JobDetailBean Summary: |
|---|
| afterPropertiesSet, getJobClass, setApplicationContext, setApplicationContextJobDataKey, setBeanName, setJobClass, setJobDataAsMap, setJobListenerNames |
| Methods from java.lang.Object: |
|---|
| equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Method from org.springframework.scheduling.quartz.JobDetailBean Detail: |
|---|
|
|
|
In case of a QuartzJobBean, the reference will be applied to the Job instance as bean property. An "applicationContext" attribute will correspond to a "setApplicationContext" method in that scenario. Note that BeanFactory callback interfaces like ApplicationContextAware are not automatically applied to Quartz Job instances, because Quartz itself is responsible for the lifecycle of its Jobs. Note: When using persistent job stores where JobDetail contents will be kept in the database, do not put an ApplicationContext reference into the JobDataMap but rather into the SchedulerContext. |
|
|
These objects will be available to this Job only, in contrast to objects in the SchedulerContext. Note: When using persistent Jobs whose JobDetail will be kept in the database, do not put Spring-managed beans or an ApplicationContext reference into the JobDataMap but rather into the SchedulerContext. |
A JobListener name always refers to the name returned by the JobListener implementation. |