Consistent *Aware callbacks for TypeFilters, ImportSelectors and ImportBeanDefinitionRegistrars [SPR-14686]

[spring-projects-issues]

Juergen Hoeller opened SPR-14686 and commented

Spring's configuration class processor provides callbacks for the common BeanClassLoaderAware, BeanFactoryAware, EnvironmentAware, and ResourceLoaderAware contracts, as known from the core BeanFactory creation algorithm. However, its callback order differs from the core BeanFactory for historic reasons: Let's finally align these for 4.3.3, since there are no side effects to expect beyond Boot (which we have immediate CI tests for).

Also, ComponentScanBeanDefinitionParser a.k.a. <context:component-scan> does not provide any such callbacks for XML-defined TypeFilter class names. Let's close that gap as well.

---

Affects: 4.3.2

Issue Links:

• Support Aware interfaces for ImportBeanDefinitionRegistrar [SPR-9568] #14202 Support Aware interfaces for ImportBeanDefinitionRegistrar
• Support *Aware ImportSelectors [SPR-10530] #15160 Support *Aware ImportSelectors
• ConfigurationClassParser does not use ApplicationContext's ResourceLoader for its MetadataReaderFactory [SPR-14684] #19248 ConfigurationClassParser does not use ApplicationContext's ResourceLoader for its MetadataReaderFactory
• ImportSelector and ImportBeanDefinitionRegistrar should be able to implement EnvironmentAware [SPR-10602] #15231 ImportSelector and ImportBeanDefinitionRegistrar should be able to implement EnvironmentAware
• Allow @ComponentScan custom filters to implement *Aware interfaces [SPR-14009] #18581 Allow @ComponentScan custom filters to implement *Aware interfaces

Referenced from: commits 09a0615, 0c2e8a6