-
Notifications
You must be signed in to change notification settings - Fork 41.4k
Register beans as RootBeanDefinition instead of GenericBeanDefinition if feasible #42611
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
Conversation
There are several places are using |
Spring Framework recommend to use |
Yes, |
I will amend it later. |
234e2a7
to
d4035a8
Compare
It's weird, this task works on my machine. |
Fixed by #42679 |
… if feasible Spring Framework recommend to use RootBeanDefinition if it's pre-determined as root bean.
This commit adapts code that was using GenericBeanDefinition to use RootBeanDefinition instead. Spring Framework recommend to use RootBeanDefinition if it's pre-determined as root bean. See gh-42611
This commit adapts code that was using GenericBeanDefinition to use RootBeanDefinition instead. Spring Framework recommend to use RootBeanDefinition if it's pre-determined as root bean. See gh-42611
Align with ConfigurationPropertiesBinder and ConfigurationPropertiesBindingPostProcessor