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

#555 No qualifier injection point prefers no qualifier bean (over named bean) #562

Merged
merged 1 commit into from
May 6, 2024

Conversation

rbygrave
Copy link
Contributor

@rbygrave rbygrave commented May 6, 2024

In the case where we have 2 beans of the same type and one has no qualifier, then when injecting a bean with no qualifier specified then prefer to wire the bean with no qualifier.

Example: In the MegaStoreManager example we have NoNameStore as a bean with no name qualifier and that is preferred for the noQualifier injection point.

…ed bean)

In the case where we have 2 beans of the same type and one has no qualifier,
then when injecting a bean with no qualifier specified then prefer to wire
the bean with no qualifier.

Example: In the MegaStoreManager example we have NoNameStore as a bean with
no name qualifier and that is preferred for the noQualifier injection point.
@rbygrave rbygrave self-assigned this May 6, 2024
@rbygrave rbygrave linked an issue May 6, 2024 that may be closed by this pull request
@rbygrave rbygrave added this to the 10.0 milestone May 6, 2024
@rbygrave rbygrave merged commit 7fb064b into master May 6, 2024
7 checks passed
@rbygrave rbygrave deleted the feature/555-noQualifierMatching branch May 6, 2024 09:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Default bean alongside the @Named one
1 participant