You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While the @Primary annotation is considered by the the bean definition obtained by the repository interface scan, it never actually makes it into the bean definition for the repository factory as that gets set up based on the information exposed via RepositoryConfiguration and the latter currently doesn't expose primary semantics.
This causes issues in case multiple extensions of a repository interface exist (or a base type and and extension) and there is code that is just supposed to work with the base type.
Affects: 1.13.23 (Ingalls SR23), 2.1.11 (Lovelace SR11), 2.2 GA (Moore)
Oliver Drotbohm opened DATACMNS-1591 and commented
While the
@Primary
annotation is considered by the the bean definition obtained by the repository interface scan, it never actually makes it into the bean definition for the repository factory as that gets set up based on the information exposed viaRepositoryConfiguration
and the latter currently doesn't expose primary semantics.This causes issues in case multiple extensions of a repository interface exist (or a base type and and extension) and there is code that is just supposed to work with the base type.
Affects: 1.13.23 (Ingalls SR23), 2.1.11 (Lovelace SR11), 2.2 GA (Moore)
Referenced from: pull request #410
Backported to: 2.2.1 (Moore SR1)
The text was updated successfully, but these errors were encountered: