Skip to content

Clarify that @Primary and @Fallback doesn't affect the sorting of beans #34212

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
wants to merge 1 commit into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,8 @@
* <p>Just like primary beans, fallback beans only have an effect when
* finding multiple candidates for single injection points.
* All type-matching beans are included when autowiring arrays,
* collections, maps, or ObjectProvider streams.
* collections, maps, or ObjectProvider streams, this annotation
* doesn't affect the sorting of beans.
*
* @author Juergen Hoeller
* @since 6.2
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,8 @@
*
* <p>Primary beans only have an effect when finding multiple candidates
* for single injection points. All type-matching beans are included when
* autowiring arrays, collections, maps, or ObjectProvider streams.
* autowiring arrays, collections, maps, or ObjectProvider streams,
* this annotation doesn't affect the sorting of beans.
*
* <p>This annotation is semantically equivalent to the {@code <bean>} element's
* {@code primary} attribute in Spring XML.
Expand Down
Loading