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

Clarify differences between GenericBeanDefinition and RootBeanDefinition #30444

Closed
snicoll opened this issue May 8, 2023 · 0 comments
Closed
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: documentation A documentation task
Milestone

Comments

@snicoll
Copy link
Member

snicoll commented May 8, 2023

Our AOT efforts has required some minor refinements in the way bean definitions are created programmatically. For an independent bean that doesn't have a parent (very common), RootBeanDefinition is a better fit, in particular as it allows to capture the resolved type early.

Looking at the Javadoc of GenericBeanDefinition it sounds like it is a better candidate for pretty much everything. It would be nice to rephrase that so that it is more accurate to the current situation.

@snicoll snicoll added type: documentation A documentation task in: core Issues in core modules (aop, beans, core, context, expression) labels May 8, 2023
@snicoll snicoll added this to the 6.0.x milestone May 8, 2023
@jhoeller jhoeller modified the milestones: 6.0.x, 6.0.10, 6.0.9 May 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: documentation A documentation task
Projects
None yet
Development

No branches or pull requests

2 participants