- All Known Subinterfaces:
- All Known Implementing Classes:
- Functional Interface:
- This is a functional interface and can therefore be used as the assignment target for a lambda expression or method reference.
Useful for custom config files targeted at system administrators that
override bean properties configured in the application context. See
PropertyResourceConfigurer and its concrete implementations for
out-of-the-box solutions that address such configuration needs.
BeanFactoryPostProcessor may interact with and modify bean
definitions, but never bean instances. Doing so may cause premature bean
instantiation, violating the container and causing unintended side effects.
If bean instance interaction is required, consider implementing
beans in its bean definitions and applies them before any other beans get created.
BeanFactoryPostProcessor may also be registered programmatically
BeanFactoryPostProcessor beans that are autodetected in an
ApplicationContext will be ordered according to
Ordered semantics. In contrast,
BeanFactoryPostProcessor beans that are registered programmatically
ConfigurableApplicationContext will be applied in the order of
registration; any ordering semantics expressed through implementing the
Ordered interface will be ignored for
programmatically registered post-processors. Furthermore, the
@Order annotation is not
taken into account for
- Juergen Hoeller, Sam Brannen
- See Also:
Method SummaryModifier and TypeMethodDescription
(ConfigurableListableBeanFactory beanFactory)Modify the application context's internal bean factory after its standard initialization.
(ConfigurableListableBeanFactory beanFactory) throws BeansExceptionModify the application context's internal bean factory after its standard initialization. All bean definitions will have been loaded, but no beans will have been instantiated yet. This allows for overriding or adding properties even to eager-initializing beans.
beanFactory- the bean factory used by the application context
BeansException- in case of errors