Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error in reference documentation sentence in part 1.8.1. Customizing Beans by Using a BeanPostProcessor [SPR-17556] #22088

spring-projects-issues opened this issue Dec 2, 2018 · 0 comments
status: backported type: documentation


Copy link

spring-projects-issues commented Dec 2, 2018

Amir Pashazadeh opened SPR-17556 and commented

In following paragraph

The org.springframework.beans.factory.config.BeanPostProcessor interface consists of 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.afterPropertiesSet(), after any declared init method) are called, and 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 it may wrap a bean with a proxy. Some Spring AOP infrastructure classes are implemented as bean post-processors in order to provide proxy-wrapping logic.

I believe after should be replaced with or,'cause statement in the parentheses is describing initializing methods.

Affects: 5.1.3

Reference URL:

Referenced from: commits 5e153e4, 4decaa2, 7a45d5f

Backported to: 5.0.12, 4.3.22

@spring-projects-issues spring-projects-issues added status: backported type: documentation labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 5.1.4 milestone Jan 11, 2019
This was referenced Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
status: backported type: documentation
None yet

No branches or pull requests

2 participants