Consistent and efficient access to BeanDefinition argument values [SPR-16192]

[spring-projects-issues]

Juergen Hoeller opened SPR-16192 and commented

Starting with a nullability mismatch between AbstractBeanDefinition.getConstructorArgumentValues/getPropertyValues and its corresponding setters (which should get addressed for the Kotlin bean DSL), it turns out that all such access can be optimized through the introduction of hasConstructorArgumentValues/hasPropertyValues methods, never enforcing the creation of those holders objects unless actually necessary. The same applies to getMethodOverrides.

---

Issue Links:

• Reduce footprint due to BeanDefinitions [SPR-7491] #12149 Reduce footprint due to BeanDefinitions
• Make getters and setters null-safety consistent [SPR-15792] #20347 Make getters and setters null-safety consistent

Referenced from: commits b5cedd4

[spring-projects-issues]

Sébastien Deleuze commented

Juergen Hoeller Very nice handling of the original issue, thanks!