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.
An ApplicationContext can autodetect BeanPostProcessor beans
in its bean definitions and apply those post-processors to any beans subsequently
created. A plain BeanFactory allows for programmatic registration of
post-processors, applying them to all beans created through the bean factory.
BeanPostProcessor beans that are autodetected in an
ApplicationContext will be ordered according to
org. and
org. semantics. In contrast,
BeanPostProcessor beans that are registered programmatically with a
BeanFactory will be applied in the order of registration; any ordering
semantics expressed through implementing the
PriorityOrdered or Ordered interface will be ignored for
programmatically registered post-processors. Furthermore, the
@Order annotation is not
taken into account for BeanPostProcessor beans.
InstantiationAwareBeanPostProcessor, DestructionAwareBeanPostProcessor, ConfigurableBeanFactory#addBeanPostProcessor, BeanFactoryPostProcessor
| Modifier and Type | Method and Description |
|---|---|
| public default Object | Returns: the bean instance to use, either the original or a wrapped one; ifnull, no subsequent BeanPostProcessors will be invokedthe new bean instance bean, String the name of the bean beanName)Apply this |
| public default Object | Returns: the bean instance to use, either the original or a wrapped one; ifnull, no subsequent BeanPostProcessors will be invokedthe new bean instance bean, String the name of the bean beanName)Apply this |
| postProcessAfterInitialization | back to summary |
|---|---|
| public default Object postProcessAfterInitialization(Object bean, String beanName) throws BeansException Apply this 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
The default implementation returns the given
| |
| postProcessBeforeInitialization | back to summary |
|---|---|
| public default Object postProcessBeforeInitialization(Object bean, String beanName) throws BeansException Apply this The default implementation returns the given
| |