Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

spring-projects-issues opened this issue Sep 9, 2016 · 0 comments


Copy link

@spring-projects-issues spring-projects-issues commented Sep 9, 2016

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:

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

Referenced from: commits 09a0615, 0c2e8a6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants