All Known Implementing Classes:
PersistenceExceptionTranslationPostProcessor, AutowiredAnnotationBeanPostProcessor, ActionServletAwareProcessor, AdvisorAdapterRegistrationManager, ScriptFactoryPostProcessor, PortletContextAwareProcessor, SimplePortletPostProcessor, RequiredAnnotationBeanPostProcessor, CommonAnnotationBeanPostProcessor, DefaultAdvisorAutoProxyCreator, AnnotationAwareAspectJAutoProxyCreator, BeanPostProcessorChecker, PersistenceAnnotationBeanPostProcessor, BootstrapContextAwareProcessor, BeanNameAutoProxyCreator, SmartInstantiationAwareBeanPostProcessor, DestructionAwareBeanPostProcessor, ServletContextAwareProcessor, SimpleServletPostProcessor, InfrastructureAdvisorAutoProxyCreator, InstantiationAwareBeanPostProcessor, InstantiationAwareBeanPostProcessorAdapter, AspectJAwareAdvisorAutoProxyCreator, MergedBeanDefinitionPostProcessor, LoadTimeWeaverAwareProcessor, AbstractAdvisorAutoProxyCreator, InitDestroyAnnotationBeanPostProcessor, ApplicationContextAwareProcessor, AbstractAutoProxyCreator
ApplicationContexts can autodetect BeanPostProcessor beans in their bean definitions and apply them to any beans subsequently created. Plain bean factories allow for programmatic registration of post-processors, applying to all beans created through this factory.
Typically, post-processors that populate beans via marker interfaces or the like will implement #postProcessBeforeInitialization , while post-processors that wrap beans with proxies will normally implement #postProcessAfterInitialization .
Juergen - Hoeller10.10.2003 - | Method from org.springframework.beans.factory.config.BeanPostProcessor Summary: |
|---|
| postProcessAfterInitialization, postProcessBeforeInitialization |
| Method from org.springframework.beans.factory.config.BeanPostProcessor Detail: |
|---|
afterPropertiesSet
or 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 This callback will also be invoked after a short-circuiting triggered by a InstantiationAwareBeanPostProcessor#postProcessBeforeInstantiation method, in contrast to all other BeanPostProcessor callbacks. |
afterPropertiesSet
or a custom init-method). The bean will already be populated with property values.
The returned bean instance may be a wrapper around the original. |