Class ScheduledAnnotationBeanPostProcessor
- All Implemented Interfaces:
- EventListener,- Aware,- BeanFactoryAware,- BeanNameAware,- BeanPostProcessor,- DestructionAwareBeanPostProcessor,- DisposableBean,- SmartInitializingSingleton,- MergedBeanDefinitionPostProcessor,- ApplicationContextAware,- ApplicationListener<ContextRefreshedEvent>,- 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 (e.g. 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
- See Also:
- 
Field SummaryFieldsModifier and TypeFieldDescriptionstatic final StringThe default name of theTaskSchedulerbean to pick up: "taskScheduler".protected final LogFields inherited from interface org.springframework.core.OrderedHIGHEST_PRECEDENCE, LOWEST_PRECEDENCE
- 
Constructor SummaryConstructorsConstructorDescriptionCreate a defaultScheduledAnnotationBeanPostProcessor.Create aScheduledAnnotationBeanPostProcessordelegating to the specifiedScheduledTaskRegistrar.
- 
Method SummaryModifier and TypeMethodDescriptionvoidInvoked right at the end of the singleton pre-instantiation phase, with a guarantee that all regular singleton beans have been created already.protected RunnablecreateRunnable(Object target, Method method) 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.voidHandle an application event.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, e.g.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.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 java.lang.Objectclone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface org.springframework.beans.factory.support.MergedBeanDefinitionPostProcessorresetBeanDefinition
- 
Field Details- 
DEFAULT_TASK_SCHEDULER_BEAN_NAMEThe 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
 
- 
- 
Constructor Details- 
ScheduledAnnotationBeanPostProcessorpublic ScheduledAnnotationBeanPostProcessor()Create a defaultScheduledAnnotationBeanPostProcessor.
- 
ScheduledAnnotationBeanPostProcessorCreate aScheduledAnnotationBeanPostProcessordelegating to the specifiedScheduledTaskRegistrar.- Parameters:
- registrar- the ScheduledTaskRegistrar to register- @Scheduledtasks on
- Since:
- 5.1
 
 
- 
- 
Method Details- 
getOrderpublic 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. 
- 
setSchedulerSet 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:
 
- 
setEmbeddedValueResolverDescription copied from interface:EmbeddedValueResolverAwareSet the StringValueResolver to use for resolving embedded definition values.- Specified by:
- setEmbeddedValueResolverin interface- EmbeddedValueResolverAware
 
- 
setBeanNameDescription 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 interface- BeanNameAware
- 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 the- BeanFactoryUtils.originalBeanName(String)method to extract the original bean name (without suffix), if desired.
 
- 
setBeanFactoryMaking aBeanFactoryavailable is optional; if not set,SchedulingConfigurerbeans won't get autodetected and aschedulerhas to be explicitly configured.- Specified by:
- setBeanFactoryin interface- BeanFactoryAware
- Parameters:
- beanFactory- owning BeanFactory (never- null). The bean can immediately call methods on the factory.
- See Also:
 
- 
setApplicationContextSetting anApplicationContextis optional: If set, registered tasks will be activated in theContextRefreshedEventphase; if not set, it will happen atafterSingletonsInstantiated()time.- Specified by:
- setApplicationContextin interface- ApplicationContextAware
- Parameters:
- applicationContext- the ApplicationContext object to be used by this object
- See Also:
 
- 
afterSingletonsInstantiatedpublic 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(java.lang.Class<T>)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 interface- SmartInitializingSingleton
 
- 
onApplicationEventDescription copied from interface:ApplicationListenerHandle an application event.- Specified by:
- onApplicationEventin interface- ApplicationListener<ContextRefreshedEvent>
- Parameters:
- event- the event to respond to
 
- 
postProcessMergedBeanDefinitionpublic 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 interface- MergedBeanDefinitionPostProcessor
- Parameters:
- beanDefinition- the merged bean definition for the bean
- beanType- the actual type of the managed bean instance
- beanName- the name of the bean
- See Also:
 
- 
postProcessBeforeInitializationDescription 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 interface- BeanPostProcessor
- Parameters:
- bean- the new bean instance
- beanName- 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:
 
- 
postProcessAfterInitializationDescription 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(java.lang.Class<?>, java.lang.String)method, in contrast to all otherBeanPostProcessorcallbacks.The default implementation returns the given beanas-is.- Specified by:
- postProcessAfterInitializationin interface- BeanPostProcessor
- Parameters:
- bean- the new bean instance
- beanName- 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:
 
- 
processScheduledProcess the given@Scheduledmethod declaration on the given bean.- Parameters:
- scheduled- the- @Scheduledannotation
- method- the method that the annotation has been declared on
- bean- the target bean instance
- See Also:
 
- 
createRunnableCreate aRunnablefor the given bean instance, calling the specified scheduled method.The default implementation creates a ScheduledMethodRunnable.- Parameters:
- target- the target bean instance
- method- the scheduled method to call
- Since:
- 5.1
- See Also:
 
- 
getScheduledTasksReturn all currently scheduled tasks, fromScheduledmethods as well as from programmaticSchedulingConfigurerinteraction.- Specified by:
- getScheduledTasksin interface- ScheduledTaskHolder
- Since:
- 5.0.2
 
- 
postProcessBeforeDestructionDescription copied from interface:DestructionAwareBeanPostProcessorApply this BeanPostProcessor to the given bean instance before its destruction, e.g. 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 interface- DestructionAwareBeanPostProcessor
- Parameters:
- bean- the bean instance to be destroyed
- beanName- the name of the bean
- See Also:
 
- 
requiresDestructionDescription 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 interface- DestructionAwareBeanPostProcessor
- Parameters:
- bean- the bean instance to check
- Returns:
- trueif- DestructionAwareBeanPostProcessor.postProcessBeforeDestruction(java.lang.Object, java.lang.String)is supposed to be called for this bean instance eventually, or- falseif not needed
 
- 
destroypublic void destroy()Description copied from interface:DisposableBeanInvoked by the containingBeanFactoryon destruction of a bean.- Specified by:
- destroyin interface- DisposableBean
 
 
-