Skip to content

InitializingBean/DisposableBean javadoc should not just refer to singletons [SPR-17131] #21668

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.

Sign up for GitHub

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

Jump to bottom
Closed
spring-projects-issues opened this issue Aug 6, 2018 · 0 comments
Closed

InitializingBean/DisposableBean javadoc should not just refer to singletons [SPR-17131] #21668

spring-projects-issues opened this issue Aug 6, 2018 · 0 comments
Assignees
@jhoeller
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: backported An issue that has been backported to maintenance branches type: task A general task
Milestone
5.0.9

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Aug 6, 2018 •
edited
Loading

Juergen Hoeller opened SPR-17131 and commented

InitializingBean and DisposableBean as well as DestructionAwareBeanPostProcessor just talk about singletons in their javadoc for historic reasons. They should refer to singletons and scoped beans, not suggesting a limitation to singletons only.

Affects: 4.3.18, 5.0.8, 5.1 RC1

Issue Links:

Referenced from: commits c814f58, f155d21, 73da153

Backported to: 4.3.19
@spring-projects-issues spring-projects-issues added status: backported An issue that has been backported to maintenance branches in: core Issues in core modules (aop, beans, core, context, expression) type: task A general task labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 5.0.9 milestone Jan 11, 2019
This was referenced Jan 11, 2019
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jhoeller jhoeller

Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: backported An issue that has been backported to maintenance branches type: task A general task
Projects
None yet
Milestone
5.0.9
Development

No branches or pull requests
2 participants
@jhoeller @spring-projects-issues