Adjus registration order of BeanDefinition declared by @Configuration #35008
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
status: waiting-for-feedback
We need additional information before we can continue
status: waiting-for-triage
An issue we've not yet triaged or decided on
While I tried to customize an
AutoConfiguration
, but@ConditionalOnBean
did not working, then I tried to find the problem through examples, source code, and the Internet, and used different configuration methods, and finally found that it was because of the registration order ofBeanDefinition
.In my opinion, their registration order should be like this:
@Import
and@EnableConfigurationProperties
)Then about
ConfigurationClassParser
, the (static)InnerConfiguration
should be managed by the fields inConfigurationClass
ofConfiguration
, and if theConditional
ofConfiguration
is not matched, then InnerConfiguration should also be skipped,ConfigurationClassBeanDefinitionReader
will be like:demo2.zip
The text was updated successfully, but these errors were encountered: