From 4decaa2da67e063ff3351c879271c5c8baf29412 Mon Sep 17 00:00:00 2001 From: Juergen Hoeller Date: Tue, 4 Dec 2018 01:20:28 +0100 Subject: [PATCH] Revised section on custom BeanPostProcessors Issue: SPR-17556 --- src/asciidoc/core-beans.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/asciidoc/core-beans.adoc b/src/asciidoc/core-beans.adoc index df41f1a3e9..f899f2c74a 100644 --- a/src/asciidoc/core-beans.adoc +++ b/src/asciidoc/core-beans.adoc @@ -3744,7 +3744,7 @@ The `BeanPostProcessor` interface defines __callback methods__ that you can impl provide your own (or override the container's default) instantiation logic, dependency-resolution logic, and so forth. If you want to implement some custom logic after the Spring container finishes instantiating, configuring, and initializing a bean, -you can plug in one or more `BeanPostProcessor` implementations. +you can plug in one or more custom `BeanPostProcessor` implementations. You can configure multiple `BeanPostProcessor` instances, and you can control the order in which these ``BeanPostProcessor``s execute by setting the `order` property. You can @@ -3776,7 +3776,7 @@ The `org.springframework.beans.factory.config.BeanPostProcessor` interface consi exactly two callback methods. When such a class is registered as a post-processor with the container, for each bean instance that is created by the container, the post-processor gets a callback from the container both __before__ container -initialization methods (such as InitializingBean's __afterPropertiesSet()__ and any +initialization methods (such as InitializingBean's __afterPropertiesSet()__ or any declared init method) are called as well as __after__ any bean initialization callbacks. The post-processor can take any action with the bean instance, including ignoring the callback completely. A bean post-processor typically checks for callback interfaces or