Class InitDestroyAnnotationBeanPostProcessor
- java.lang.Object
- org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor
- All Implemented Interfaces:
Serializable,BeanPostProcessor,DestructionAwareBeanPostProcessor,MergedBeanDefinitionPostProcessor,Ordered,PriorityOrdered
- Direct Known Subclasses:
CommonAnnotationBeanPostProcessor
public class InitDestroyAnnotationBeanPostProcessor extends Object implements DestructionAwareBeanPostProcessor, MergedBeanDefinitionPostProcessor, PriorityOrdered, Serializable
BeanPostProcessorimplementation that invokes annotated init and destroy methods. Allows for an annotation alternative to Spring'sInitializingBeanandDisposableBeancallback interfaces.The actual annotation types that this post-processor checks for can be configured through the
"initAnnotationType"and"destroyAnnotationType"properties. Any custom annotation can be used, since there are no required annotation attributes.Init and destroy annotations may be applied to methods of any visibility: public, package-protected, protected, or private. Multiple such methods may be annotated, but it is recommended to only annotate one single init method and destroy method, respectively.
Spring's
CommonAnnotationBeanPostProcessorsupports the JSR-250PostConstructandPreDestroyannotations out of the box, as init annotation and destroy annotation, respectively. Furthermore, it also supports theResourceannotation for annotation-driven injection of named beans.
Field Summary
Fields inherited from interface org.springframework.core.Ordered
HIGHEST_PRECEDENCE, LOWEST_PRECEDENCE
Constructor Summary
Constructors Constructor Description InitDestroyAnnotationBeanPostProcessor()
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description intgetOrder()Get the order value of this object.ObjectpostProcessAfterInitialization(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.ObjectpostProcessBeforeInitialization(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.booleanrequiresDestruction(Object bean)Determine whether the given bean instance requires destruction by this post-processor.voidsetDestroyAnnotationType(Class<? extends Annotation> destroyAnnotationType)Specify the destroy annotation to check for, indicating destruction methods to call when the context is shutting down.voidsetInitAnnotationType(Class<? extends Annotation> initAnnotationType)Specify the init annotation to check for, indicating initialization methods to call after configuration of a bean.voidsetOrder(int order)Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
Methods inherited from interface org.springframework.beans.factory.support.MergedBeanDefinitionPostProcessor
resetBeanDefinition
Constructor Detail
InitDestroyAnnotationBeanPostProcessor
public InitDestroyAnnotationBeanPostProcessor()
Method Detail
setInitAnnotationType
public void setInitAnnotationType(Class<? extends Annotation> initAnnotationType)
Specify the init annotation to check for, indicating initialization methods to call after configuration of a bean.Any custom annotation can be used, since there are no required annotation attributes. There is no default, although a typical choice is the JSR-250
PostConstructannotation.
setDestroyAnnotationType
public void setDestroyAnnotationType(Class<? extends Annotation> destroyAnnotationType)
Specify the destroy annotation to check for, indicating destruction methods to call when the context is shutting down.Any custom annotation can be used, since there are no required annotation attributes. There is no default, although a typical choice is the JSR-250
PreDestroyannotation.
setOrder
public void setOrder(int order)
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.
- Specified by:
getOrderin interfaceOrdered- Returns:
- the order value
- See Also:
Ordered.HIGHEST_PRECEDENCE,Ordered.LOWEST_PRECEDENCE
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:
AbstractAutowireCapableBeanFactory.applyMergedBeanDefinitionPostProcessors(org.springframework.beans.factory.support.RootBeanDefinition, java.lang.Class<?>, java.lang.String)
postProcessBeforeInitialization
public Object postProcessBeforeInitialization(Object bean, String beanName) throws BeansException
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 - Throws:
BeansException- in case of errors- See Also:
InitializingBean.afterPropertiesSet()
postProcessAfterInitialization
public Object postProcessAfterInitialization(Object bean, String beanName) throws BeansException
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(java.lang.Class<?>, java.lang.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 - Throws:
BeansException- in case of errors- See Also:
InitializingBean.afterPropertiesSet(),FactoryBean
postProcessBeforeDestruction
public void postProcessBeforeDestruction(Object bean, String beanName) throws BeansException
Description 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 interfaceDestructionAwareBeanPostProcessor- Parameters:
bean- the bean instance to be destroyedbeanName- the name of the bean- Throws:
BeansException- in case of errors- See Also:
DisposableBean.destroy(),AbstractBeanDefinition.setDestroyMethodName(String)
requiresDestruction
public boolean requiresDestruction(Object bean)
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(java.lang.Object, java.lang.String)is supposed to be called for this bean instance eventually, orfalseif not needed