diff --git a/spring-framework-reference/src/beans-extension-points.xml b/spring-framework-reference/src/beans-extension-points.xml index e0c9747cfe3..1bcc09886af 100644 --- a/spring-framework-reference/src/beans-extension-points.xml +++ b/spring-framework-reference/src/beans-extension-points.xml @@ -283,15 +283,14 @@ org.springframework.scripting.groovy.GroovyMessenger@272961 would any other bean. - As with BeanPostProcessors, you typically do not - want BeanFactoryPostProcessors marked as - lazy-initialized. If they are marked as such, the Spring container never - instantiates them, and thus they cannot apply their custom logic. If you - use the default-lazy-init attribute on the - declaration of your <beans/> element, be sure - to mark your various - BeanFactoryPostProcessor bean definitions - with lazy-init="false". + As with BeanPostProcessors, you typically + do not want BeanFactoryPostProcessors marked as + lazy-initialized. If no other bean references a Bean(Factory)PostProcessor + those wouldn't get instantiated at all. Thus, marking them as + lazy-initialized will be ignored and the Bean(Factory)PostProcessor + will be instantied eagerly even if you use the default-lazy-init + attribute set to trueon the declaration of your + element.