BeanFactoryPostProcessor implementations should not be instantiated via constructor dependency injection.
#917
Comments
alaneuler
changed the title
BeanFactoryPostProcessor implementations should not be instantiated via constructor.BeanFactoryPostProcessor implementations should not be instantiated via constructor dependency injection.
|
Similar issue: spring-projects/spring-framework#28122 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Spring, constructor dependency injection is only available by means of inject-by-type. If
BeanFactoryPostProcessorimplementations is created via constructor, it will make Spring invokeBeanFactoryUtils.beanNamesForTypeIncludingAncestorsto find all suitable candidates. And because of that, bean type unknown unless initialized will be created way early (invokeBeanFactoryPostProcessorsphase), e.g.,FactoryBean.Thus we should abandon the usage of creating
BeanFactoryPostProcessorimplementations via constructor:SofaModuleBeanFactoryPostProcessorRuntimeContextBeanFactoryPostProcessorServiceBeanFactoryPostProcessorThe text was updated successfully, but these errors were encountered: