Class ScheduledAnnotationBeanPostProcessor
- All Implemented Interfaces:
EventListener, Aware, BeanFactoryAware, BeanNameAware, BeanPostProcessor, DestructionAwareBeanPostProcessor, DisposableBean, SmartInitializingSingleton, MergedBeanDefinitionPostProcessor, ApplicationContextAware, ApplicationListener<ApplicationContextEvent>, EmbeddedValueResolverAware, Ordered, ScheduledTaskHolder
@Scheduled to be invoked by a
TaskScheduler according to the
"fixedRate", "fixedDelay", or "cron" expression provided via the annotation.
This post-processor is automatically registered by Spring's
<task:annotation-driven> XML element and also by the
@EnableScheduling annotation.
Autodetects any SchedulingConfigurer instances in the container,
allowing for customization of the scheduler to be used or for fine-grained
control over task registration (for example, registration of Trigger tasks).
See the @EnableScheduling javadocs for complete usage
details.
- Since:
- 3.0
- Author:
- Mark Fisher, Juergen Hoeller, Chris Beams, Elizabeth Chatman, Victor Brown, Sam Brannen, Simon Baslé
- See Also:
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final StringThe default name of theTaskSchedulerbean to pick up: "taskScheduler".protected final org.apache.commons.logging.LogFields inherited from interface Ordered
HIGHEST_PRECEDENCE, LOWEST_PRECEDENCE -
Constructor Summary
ConstructorsConstructorDescriptionCreate a defaultScheduledAnnotationBeanPostProcessor.Create aScheduledAnnotationBeanPostProcessordelegating to the specifiedScheduledTaskRegistrar. -
Method Summary
Modifier and TypeMethodDescriptionvoidInvoked right at the end of the singleton pre-instantiation phase, with a guarantee that all regular singleton beans have been created already.createRunnable(Object target, Method method) Deprecated.protected RunnablecreateRunnable(Object target, Method method, @Nullable String qualifier) Create aRunnablefor the given bean instance, calling the specified scheduled method.voiddestroy()Invoked by the containingBeanFactoryon destruction of a bean.intgetOrder()Get the order value of this object.Return all currently scheduled tasks, fromScheduledmethods as well as from programmaticSchedulingConfigurerinteraction.voidReacts toContextRefreshedEventas well asContextClosedEvent: performingfinishRegistration()and early cancelling of scheduled tasks, respectively.postProcessAfterInitialization(Object bean, String beanName) Apply thisBeanPostProcessorto the given new bean instance after any bean initialization callbacks (like InitializingBean'safterPropertiesSetor a custom init-method).voidpostProcessBeforeDestruction(Object bean, String beanName) Apply this BeanPostProcessor to the given bean instance before its destruction, for example, invoking custom destruction callbacks.postProcessBeforeInitialization(Object bean, String beanName) Apply thisBeanPostProcessorto the given new bean instance before any bean initialization callbacks (like InitializingBean'safterPropertiesSetor a custom init-method).voidpostProcessMergedBeanDefinition(RootBeanDefinition beanDefinition, Class<?> beanType, String beanName) Post-process the given merged bean definition for the specified bean.protected voidprocessScheduled(Scheduled scheduled, Method method, Object bean) Process the given@Scheduledmethod declaration on the given bean, attempting to distinguish reactive methods from synchronous methods.booleanrequiresDestruction(Object bean) Determine whether the given bean instance requires destruction by this post-processor.voidsetApplicationContext(ApplicationContext applicationContext) Setting anApplicationContextis optional: If set, registered tasks will be activated in theContextRefreshedEventphase; if not set, it will happen atafterSingletonsInstantiated()time.voidsetBeanFactory(BeanFactory beanFactory) Making aBeanFactoryavailable is optional; if not set,SchedulingConfigurerbeans won't get autodetected and aschedulerhas to be explicitly configured.voidsetBeanName(String beanName) Set the name of the bean in the bean factory that created this bean.voidsetEmbeddedValueResolver(StringValueResolver resolver) Set the StringValueResolver to use for resolving embedded definition values.voidsetScheduler(Object scheduler) Set theTaskSchedulerthat will invoke the scheduled methods, or aScheduledExecutorServiceto be wrapped as a TaskScheduler.Methods inherited from class Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface ApplicationListener
supportsAsyncExecutionMethods inherited from interface MergedBeanDefinitionPostProcessor
resetBeanDefinition
-
Field Details
-
DEFAULT_TASK_SCHEDULER_BEAN_NAME
The default name of theTaskSchedulerbean to pick up: "taskScheduler".Note that the initial lookup happens by type; this is just the fallback in case of multiple scheduler beans found in the context.
- Since:
- 4.2
- See Also:
-
logger
protected final org.apache.commons.logging.Log logger
-
-
Constructor Details
-
ScheduledAnnotationBeanPostProcessor
public ScheduledAnnotationBeanPostProcessor()Create a defaultScheduledAnnotationBeanPostProcessor. -
ScheduledAnnotationBeanPostProcessor
Create aScheduledAnnotationBeanPostProcessordelegating to the specifiedScheduledTaskRegistrar.- Parameters:
registrar- the ScheduledTaskRegistrar to register@Scheduledtasks on- Since:
- 5.1
-
-
Method Details
-
getOrder
public int getOrder()Description copied from interface:OrderedGet the order value of this object.Higher values are interpreted as lower priority. As a consequence, the object with the lowest value has the highest priority (somewhat analogous to Servlet
load-on-startupvalues).Same order values will result in arbitrary sort positions for the affected objects.
-
setScheduler
Set theTaskSchedulerthat will invoke the scheduled methods, or aScheduledExecutorServiceto be wrapped as a TaskScheduler.If not specified, default scheduler resolution will apply: searching for a unique
TaskSchedulerbean in the context, or for aTaskSchedulerbean named "taskScheduler" otherwise; the same lookup will also be performed for aScheduledExecutorServicebean. If neither of the two is resolvable, a local single-threaded default scheduler will be created within the registrar.- See Also:
-
setEmbeddedValueResolver
Description copied from interface:EmbeddedValueResolverAwareSet the StringValueResolver to use for resolving embedded definition values.- Specified by:
setEmbeddedValueResolverin interfaceEmbeddedValueResolverAware
-
setBeanName
Description copied from interface:BeanNameAwareSet the name of the bean in the bean factory that created this bean.Invoked after population of normal bean properties but before an init callback such as
InitializingBean.afterPropertiesSet()or a custom init-method.- Specified by:
setBeanNamein interfaceBeanNameAware- Parameters:
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 theBeanFactoryUtils.originalBeanName(String)method to extract the original bean name (without suffix), if desired.
-
setBeanFactory
Making aBeanFactoryavailable is optional; if not set,SchedulingConfigurerbeans won't get autodetected and aschedulerhas to be explicitly configured.- Specified by:
setBeanFactoryin interfaceBeanFactoryAware- Parameters:
beanFactory- owning BeanFactory (nevernull). The bean can immediately call methods on the factory.- See Also:
-
setApplicationContext
Setting anApplicationContextis optional: If set, registered tasks will be activated in theContextRefreshedEventphase; if not set, it will happen atafterSingletonsInstantiated()time.- Specified by:
setApplicationContextin interfaceApplicationContextAware- Parameters:
applicationContext- the ApplicationContext object to be used by this object- See Also:
-
afterSingletonsInstantiated
public void afterSingletonsInstantiated()Description copied from interface:SmartInitializingSingletonInvoked right at the end of the singleton pre-instantiation phase, with a guarantee that all regular singleton beans have been created already.ListableBeanFactory.getBeansOfType(Class)calls within this method won't trigger accidental side effects during bootstrap.NOTE: This callback won't be triggered for singleton beans lazily initialized on demand after
BeanFactorybootstrap, and not for any other bean scope either. Carefully use it for beans with the intended bootstrap semantics only.- Specified by:
afterSingletonsInstantiatedin interfaceSmartInitializingSingleton
-
postProcessMergedBeanDefinition
public void postProcessMergedBeanDefinition(RootBeanDefinition beanDefinition, Class<?> beanType, String beanName) Description copied from interface:MergedBeanDefinitionPostProcessorPost-process the given merged bean definition for the specified bean.- Specified by:
postProcessMergedBeanDefinitionin interfaceMergedBeanDefinitionPostProcessor- Parameters:
beanDefinition- the merged bean definition for the beanbeanType- the actual type of the managed bean instancebeanName- the name of the bean- See Also:
-
postProcessBeforeInitialization
Description copied from interface:BeanPostProcessorApply thisBeanPostProcessorto the given new bean instance before any bean initialization callbacks (like InitializingBean'safterPropertiesSetor a custom init-method). The bean will already be populated with property values. The returned bean instance may be a wrapper around the original.The default implementation returns the given
beanas-is.- Specified by:
postProcessBeforeInitializationin interfaceBeanPostProcessor- Parameters:
bean- the new bean instancebeanName- the name of the bean- Returns:
- the bean instance to use, either the original or a wrapped one;
if
null, no subsequent BeanPostProcessors will be invoked - See Also:
-
postProcessAfterInitialization
Description copied from interface:BeanPostProcessorApply thisBeanPostProcessorto the given new bean instance after any bean initialization callbacks (like InitializingBean'safterPropertiesSetor a custom init-method). The bean will already be populated with property values. The returned bean instance may be a wrapper around the original.In case of a FactoryBean, this callback will be invoked for both the FactoryBean instance and the objects created by the FactoryBean (as of Spring 2.0). The post-processor can decide whether to apply to either the FactoryBean or created objects or both through corresponding
bean instanceof FactoryBeanchecks.This callback will also be invoked after a short-circuiting triggered by a
InstantiationAwareBeanPostProcessor.postProcessBeforeInstantiation(Class, String)method, in contrast to all otherBeanPostProcessorcallbacks.The default implementation returns the given
beanas-is.- Specified by:
postProcessAfterInitializationin interfaceBeanPostProcessor- Parameters:
bean- the new bean instancebeanName- the name of the bean- Returns:
- the bean instance to use, either the original or a wrapped one;
if
null, no subsequent BeanPostProcessors will be invoked - See Also:
-
processScheduled
Process the given@Scheduledmethod declaration on the given bean, attempting to distinguish reactive methods from synchronous methods.- Parameters:
scheduled- the@Scheduledannotationmethod- the method that the annotation has been declared onbean- the target bean instance- See Also:
-
createRunnable
Create aRunnablefor the given bean instance, calling the specified scheduled method.The default implementation creates a
ScheduledMethodRunnable.- Parameters:
target- the target bean instancemethod- the scheduled method to call- Since:
- 6.1
-
createRunnable
Deprecated.in favor ofcreateRunnable(Object, Method, String)Create aRunnablefor the given bean instance, calling the specified scheduled method.- Parameters:
target- the target bean instancemethod- the scheduled method to call- Since:
- 5.1
-
getScheduledTasks
Return all currently scheduled tasks, fromScheduledmethods as well as from programmaticSchedulingConfigurerinteraction.Note that this includes upcoming scheduled subscriptions for reactive methods but doesn't cover any currently active subscription for such methods.
- Specified by:
getScheduledTasksin interfaceScheduledTaskHolder- Since:
- 5.0.2
-
postProcessBeforeDestruction
Description copied from interface:DestructionAwareBeanPostProcessorApply this BeanPostProcessor to the given bean instance before its destruction, for example, invoking custom destruction callbacks.Like DisposableBean's
destroyand a custom destroy method, this callback will only apply to beans which the container fully manages the lifecycle for. This is usually the case for singletons and scoped beans.- Specified by:
postProcessBeforeDestructionin interfaceDestructionAwareBeanPostProcessor- Parameters:
bean- the bean instance to be destroyedbeanName- the name of the bean- See Also:
-
requiresDestruction
Description copied from interface:DestructionAwareBeanPostProcessorDetermine whether the given bean instance requires destruction by this post-processor.The default implementation returns
true. If a pre-5 implementation ofDestructionAwareBeanPostProcessordoes not provide a concrete implementation of this method, Spring silently assumestrueas well.- Specified by:
requiresDestructionin interfaceDestructionAwareBeanPostProcessor- Parameters:
bean- the bean instance to check- Returns:
trueifDestructionAwareBeanPostProcessor.postProcessBeforeDestruction(Object, String)is supposed to be called for this bean instance eventually, orfalseif not needed
-
destroy
public void destroy()Description copied from interface:DisposableBeanInvoked by the containingBeanFactoryon destruction of a bean.- Specified by:
destroyin interfaceDisposableBean
-
onApplicationEvent
Reacts toContextRefreshedEventas well asContextClosedEvent: performingfinishRegistration()and early cancelling of scheduled tasks, respectively.- Specified by:
onApplicationEventin interfaceApplicationListener<ApplicationContextEvent>- Parameters:
event- the event to respond to
-
createRunnable(Object, Method, String)