Skip to content

Detect late-set primary markers for autowiring shortcut algorithm #34658

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

Closed
jhoeller opened this issue Mar 26, 2025 · 0 comments
Closed

Detect late-set primary markers for autowiring shortcut algorithm #34658

jhoeller opened this issue Mar 26, 2025 · 0 comments
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: bug A general bug
Milestone

Comments

@jhoeller
Copy link
Contributor

The autowiring shortcut introduced in 6.2 (#28122) relies on potentially conflicting primary beans being known at injection time. Late-set primary markers in a BeanFactoryPostProcessor need to get consistently detected and taken into account as well, allowing the shortcut algorithm to back out if any such primary-marked bean matches the injection type (overriding a bean name match for the field/parameter name).

@jhoeller jhoeller added the type: bug A general bug label Mar 26, 2025
@jhoeller jhoeller added this to the 6.2.6 milestone Mar 26, 2025
@jhoeller jhoeller self-assigned this Mar 26, 2025
@jhoeller jhoeller added the in: core Issues in core modules (aop, beans, core, context, expression) label Mar 26, 2025
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) type: bug A general bug
Projects
None yet
Development

No branches or pull requests

1 participant