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

addCandidateComponentsFromIndex should create ScannedGenericBeanDefinitions #24638

Closed
abenneke opened this issue Mar 4, 2020 · 0 comments
Closed
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: backported An issue that has been backported to maintenance branches type: bug A general bug
Milestone

Comments

@abenneke
Copy link

abenneke commented Mar 4, 2020

Is there a special reason why ClassPathScanningCandidateComponentProvider.addCandidateComponentsFromIndex does create AnnotatedGenericBeanDefinitions while scanCandidateComponents creates ScannedGenericBeanDefinitions?

Without this ScannedGenericBeanDefinitions in ConfigurationClassBeanDefinitionReader.isOverriddenByExistingDefinition the bean definitions created from the index are treated different than the scanned bean definitions and overriding no longer works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: backported An issue that has been backported to maintenance branches type: bug A general bug
Projects
None yet
Development

No branches or pull requests

3 participants