接口 BeanPostProcessor
- 所有已知子接口:
DestructionAwareBeanPostProcessor,InstantiationAwareBeanPostProcessor,MergedBeanDefinitionPostProcessor,SmartInstantiationAwareBeanPostProcessor
- 所有已知实现类:
AbstractAdvisingBeanPostProcessor,AbstractAdvisorAutoProxyCreator,AbstractAutoProxyCreator,AbstractBeanFactoryAwareAdvisingPostProcessor,AdvisorAdapterRegistrationManager,AnnotationAwareAspectJAutoProxyCreator,AspectJAwareAdvisorAutoProxyCreator,AsyncAnnotationBeanPostProcessor,AutowiredAnnotationBeanPostProcessor,BeanNameAutoProxyCreator,BeanValidationPostProcessor,CommonAnnotationBeanPostProcessor,DefaultAdvisorAutoProxyCreator,InfrastructureAdvisorAutoProxyCreator,InitDestroyAnnotationBeanPostProcessor,InstantiationAwareBeanPostProcessorAdapter,JmsListenerAnnotationBeanPostProcessor,LoadTimeWeaverAwareProcessor,MethodValidationPostProcessor,PersistenceAnnotationBeanPostProcessor,PersistenceExceptionTranslationPostProcessor,RequiredAnnotationBeanPostProcessor,ScheduledAnnotationBeanPostProcessor,ScriptFactoryPostProcessor,ServletContextAwareProcessor,SimpleServletPostProcessor
public interface BeanPostProcessor
Factory hook that allows for custom modification of new bean instances — for example, checking for marker interfaces or wrapping beans with proxies.Typically, post-processors that populate beans via marker interfaces or the like will implement
postProcessBeforeInitialization(java.lang.Object, java.lang.String), while post-processors that wrap beans with proxies will normally implementpostProcessAfterInitialization(java.lang.Object, java.lang.String).Registration
An
ApplicationContextcan autodetectBeanPostProcessorbeans in its bean definitions and apply those post-processors to any beans subsequently created. A plainBeanFactoryallows for programmatic registration of post-processors, applying them to all beans created through the bean factory.Ordering
BeanPostProcessorbeans that are autodetected in anApplicationContextwill be ordered according toPriorityOrderedandOrderedsemantics. In contrast,BeanPostProcessorbeans that are registered programmatically with aBeanFactorywill be applied in the order of registration; any ordering semantics expressed through implementing thePriorityOrderedorOrderedinterface will be ignored for programmatically registered post-processors. Furthermore, the@Orderannotation is not taken into account forBeanPostProcessorbeans.- 从以下版本开始:
- 10.10.2003
- 作者:
- Juergen Hoeller, Sam Brannen
- 另请参阅:
InstantiationAwareBeanPostProcessor,DestructionAwareBeanPostProcessor,ConfigurableBeanFactory.addBeanPostProcessor(org.springframework.beans.factory.config.BeanPostProcessor),BeanFactoryPostProcessor
方法概要
所有方法 实例方法 默认方法 修饰符和类型 方法 说明 default ObjectpostProcessAfterInitialization(Object bean, String beanName)Apply thisBeanPostProcessorto the given new bean instance after any bean initialization callbacks (like InitializingBean'safterPropertiesSetor a custom init-method).default ObjectpostProcessBeforeInitialization(Object bean, String beanName)Apply thisBeanPostProcessorto the given new bean instance before any bean initialization callbacks (like InitializingBean'safterPropertiesSetor a custom init-method).
方法详细资料
postProcessBeforeInitialization
@Nullable default Object postProcessBeforeInitialization(Object bean, String beanName) throws BeansException
Apply 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.- 参数:
bean- the new bean instancebeanName- the name of the bean- 返回:
- the bean instance to use, either the original or a wrapped one; if
null, no subsequent BeanPostProcessors will be invoked - 抛出:
BeansException- in case of errors- 另请参阅:
InitializingBean.afterPropertiesSet()
postProcessAfterInitialization
@Nullable default Object postProcessAfterInitialization(Object bean, String beanName) throws BeansException
Apply 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.- 参数:
bean- the new bean instancebeanName- the name of the bean- 返回:
- the bean instance to use, either the original or a wrapped one; if
null, no subsequent BeanPostProcessors will be invoked - 抛出:
BeansException- in case of errors- 另请参阅:
InitializingBean.afterPropertiesSet(),FactoryBean