public class JobDetailFactoryBean extends java.lang.Object implements FactoryBean<JobDetail>, BeanNameAware, ApplicationContextAware, InitializingBean
FactoryBean
for creating a Quartz org.quartz.JobDetail
instance, supporting bean-style usage for JobDetail configuration.
JobDetail(Impl)
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.
NOTE: This FactoryBean works against both Quartz 1.x and Quartz 2.x,
in contrast to the older JobDetailBean
class.
setName(java.lang.String)
,
setGroup(java.lang.String)
,
BeanNameAware
,
org.quartz.Scheduler#DEFAULT_GROUP
Modifier and Type | Field and Description |
---|---|
private ApplicationContext |
applicationContext |
private java.lang.String |
applicationContextJobDataKey |
private java.lang.String |
beanName |
private java.lang.String |
description |
private boolean |
durability |
private java.lang.String |
group |
private java.lang.Class |
jobClass |
private JobDataMap |
jobDataMap |
private JobDetail |
jobDetail |
private java.lang.String |
name |
private boolean |
requestsRecovery |
Constructor and Description |
---|
JobDetailFactoryBean() |
Modifier and Type | Method and Description |
---|---|
void |
afterPropertiesSet()
Invoked by a BeanFactory after it has set all bean properties supplied
(and satisfied BeanFactoryAware and ApplicationContextAware).
|
JobDataMap |
getJobDataMap()
Return the job's JobDataMap.
|
JobDetail |
getObject()
Return an instance (possibly shared or independent) of the object
managed by this factory.
|
java.lang.Class<?> |
getObjectType()
Return the type of object that this FactoryBean creates,
or
null if not known in advance. |
boolean |
isSingleton()
Is the object managed by this factory a singleton? That is,
will
FactoryBean.getObject() always return the same object
(a reference that can be cached)? |
void |
setApplicationContext(ApplicationContext applicationContext)
Set the ApplicationContext that this object runs in.
|
void |
setApplicationContextJobDataKey(java.lang.String applicationContextJobDataKey)
Set the key of an ApplicationContext reference to expose in the JobDataMap,
for example "applicationContext".
|
void |
setBeanName(java.lang.String beanName)
Set the name of the bean in the bean factory that created this bean.
|
void |
setDescription(java.lang.String description)
Set a textual description for this job.
|
void |
setDurability(boolean durability)
Specify the job's durability, i.e.
|
void |
setGroup(java.lang.String group)
Specify the job's group.
|
void |
setJobClass(java.lang.Class jobClass)
Specify the job's implementation class.
|
void |
setJobDataAsMap(java.util.Map<java.lang.String,?> jobDataAsMap)
Register objects in the JobDataMap via a given Map.
|
void |
setJobDataMap(JobDataMap jobDataMap)
Set the job's JobDataMap.
|
void |
setName(java.lang.String name)
Specify the job's name.
|
void |
setRequestsRecovery(boolean requestsRecovery)
Set the recovery flag for this job, i.e.
|
private java.lang.String name
private java.lang.String group
private java.lang.Class jobClass
private JobDataMap jobDataMap
private boolean durability
private boolean requestsRecovery
private java.lang.String description
private java.lang.String beanName
private ApplicationContext applicationContext
private java.lang.String applicationContextJobDataKey
private JobDetail jobDetail
public void setName(java.lang.String name)
public void setGroup(java.lang.String group)
public void setJobClass(java.lang.Class jobClass)
public void setJobDataMap(JobDataMap jobDataMap)
public JobDataMap getJobDataMap()
public void setJobDataAsMap(java.util.Map<java.lang.String,?> jobDataAsMap)
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.
jobDataAsMap
- Map with String keys and any objects as values
(for example Spring-managed beans)SchedulerFactoryBean.setSchedulerContextAsMap(java.util.Map)
public void setDurability(boolean durability)
public void setRequestsRecovery(boolean requestsRecovery)
public void setDescription(java.lang.String description)
public void setBeanName(java.lang.String beanName)
BeanNameAware
Invoked after population of normal bean properties but before an
init callback such as InitializingBean.afterPropertiesSet()
or a custom init-method.
setBeanName
in interface BeanNameAware
beanName
- the name of the bean in the factory.
Note that this name is the actual bean name used in the factory, which may
differ from the originally specified name: in particular for inner bean
names, the actual bean name might have been made unique through appending
"#..." suffixes. Use the BeanFactoryUtils.originalBeanName(String)
method to extract the original bean name (without suffix), if desired.public void setApplicationContext(ApplicationContext applicationContext)
ApplicationContextAware
Invoked after population of normal bean properties but before an init callback such
as InitializingBean.afterPropertiesSet()
or a custom init-method. Invoked after ResourceLoaderAware.setResourceLoader(org.springframework.core.io.ResourceLoader)
,
ApplicationEventPublisherAware.setApplicationEventPublisher(org.springframework.context.ApplicationEventPublisher)
and
MessageSourceAware
, if applicable.
setApplicationContext
in interface ApplicationContextAware
applicationContext
- the ApplicationContext object to be used by this objectBeanInitializationException
public void setApplicationContextJobDataKey(java.lang.String applicationContextJobDataKey)
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.
public void afterPropertiesSet()
InitializingBean
This method allows the bean instance to perform initialization only possible when all bean properties have been set and to throw an exception in the event of misconfiguration.
afterPropertiesSet
in interface InitializingBean
public JobDetail getObject()
FactoryBean
As with a BeanFactory
, this allows support for both the
Singleton and Prototype design pattern.
If this FactoryBean is not fully initialized yet at the time of
the call (for example because it is involved in a circular reference),
throw a corresponding FactoryBeanNotInitializedException
.
As of Spring 2.0, FactoryBeans are allowed to return null
objects. The factory will consider this as normal value to be used; it
will not throw a FactoryBeanNotInitializedException in this case anymore.
FactoryBean implementations are encouraged to throw
FactoryBeanNotInitializedException themselves now, as appropriate.
getObject
in interface FactoryBean<JobDetail>
null
)FactoryBeanNotInitializedException
public java.lang.Class<?> getObjectType()
FactoryBean
null
if not known in advance.
This allows one to check for specific types of beans without instantiating objects, for example on autowiring.
In the case of implementations that are creating a singleton object, this method should try to avoid singleton creation as far as possible; it should rather estimate the type in advance. For prototypes, returning a meaningful type here is advisable too.
This method can be called before this FactoryBean has been fully initialized. It must not rely on state created during initialization; of course, it can still use such state if available.
NOTE: Autowiring will simply ignore FactoryBeans that return
null
here. Therefore it is highly recommended to implement
this method properly, using the current state of the FactoryBean.
getObjectType
in interface FactoryBean<JobDetail>
null
if not known at the time of the callListableBeanFactory.getBeansOfType(java.lang.Class<T>)
public boolean isSingleton()
FactoryBean
FactoryBean.getObject()
always return the same object
(a reference that can be cached)?
NOTE: If a FactoryBean indicates to hold a singleton object,
the object returned from getObject()
might get cached
by the owning BeanFactory. Hence, do not return true
unless the FactoryBean always exposes the same reference.
The singleton status of the FactoryBean itself will generally be provided by the owning BeanFactory; usually, it has to be defined as singleton there.
NOTE: This method returning false
does not
necessarily indicate that returned objects are independent instances.
An implementation of the extended SmartFactoryBean
interface
may explicitly indicate independent instances through its
SmartFactoryBean.isPrototype()
method. Plain FactoryBean
implementations which do not implement this extended interface are
simply assumed to always return independent instances if the
isSingleton()
implementation returns false
.
isSingleton
in interface FactoryBean<JobDetail>
FactoryBean.getObject()
,
SmartFactoryBean.isPrototype()