Provide BeanDefinitionRegistryPostProcessor lifecycle hook [SPR-5595] #10266
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
type: enhancement
A general enhancement
Milestone
Chris Beams opened SPR-5595 and commented
Per discussions around
@Configuration
class processing, ConfigurationClassPostProcessor (currently a BeanFactoryPostProcessor) really needs a distinct new lifecycle hook for post-processing the BeanDefinitionRegistry. This hook should happen right before BeanFactoryPostProcessing. It gives the framework a first-class opportunity to detect, enhance and process@Configuration
class BeanDefinitions and register new BeanDefinitions into the BeanDefintitionRegistry for each@Bean
method parsed.Affected classes will be:
This change also has implications for Spring IDE. The current plan is that Spring IDE will detect the presence of the ConfigurationClassPostProcessor and invoke its own
@Configuration
class processing lifecycle. If a BeanDefinitionRegistryPostProcessor lifecycle is introduced, Spring IDE will have to accomodate this change accordingly.No further details from SPR-5595
The text was updated successfully, but these errors were encountered: