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.
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 ofhasConstructorArgumentValues/hasPropertyValues
methods, never enforcing the creation of those holders objects unless actually necessary. The same applies togetMethodOverrides
.Issue Links:
Referenced from: commits b5cedd4
The text was updated successfully, but these errors were encountered: