You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are quite a few "helper" beans, e.g. related to processing @ConfigurationProperties, and they all get manually registered as GenericBeanDefinitions with reflection-based instantiation strategies. Probably this is unnecessary (unless there are visibility issues, which also would need to be addressed if we change this). In the package "org.springframework.boot.context.properties" I see bean definitions registered for ConfigurationPropertiesBeanDefinitionValidator, ConfigurationPropertiesBindingPostProcessor, BoundConfigurationProperties, ConfigurationBeanFactoryMetadata, ConfigurationPropertiesBinder and ConfigurationPropertiesBinder$Factory, for instance. Searching for usage of GenericBeanDefinition and RootBeanDefinition will show up about the same number again in various places.
The text was updated successfully, but these errors were encountered:
wilkinsona
changed the title
Switch to reflection-free configuration for infrastructure where GenericBeanDefinition is used currently
Switch to reflection-free configuration for infrastructure where bean definitions are created manually
Jul 14, 2020
There are quite a few "helper" beans, e.g. related to processing
@ConfigurationProperties
, and they all get manually registered asGenericBeanDefinitions
with reflection-based instantiation strategies. Probably this is unnecessary (unless there are visibility issues, which also would need to be addressed if we change this). In the package "org.springframework.boot.context.properties" I see bean definitions registered forConfigurationPropertiesBeanDefinitionValidator
,ConfigurationPropertiesBindingPostProcessor
,BoundConfigurationProperties
,ConfigurationBeanFactoryMetadata
,ConfigurationPropertiesBinder
andConfigurationPropertiesBinder$Factory
, for instance. Searching for usage ofGenericBeanDefinition
andRootBeanDefinition
will show up about the same number again in various places.The text was updated successfully, but these errors were encountered: