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
We could expand the type information that we expose via BeanDefinition.setTargetType(…) by inspecting domain and identifier type from the RepositoryMetadata. This is in response to setting that type blessed by the fix for spring-projects/spring-framework#32489.
The text was updated successfully, but these errors were encountered:
We now also forward the domain and identifier information detected on the repository to the target type declared for the repository factory bean definition.
FixesGH-3074.
…ort extensions.
Spring Data modules might override, and, by that, fix some of the generic type parameters exposed by RepositoryFactoryBeanSupport. We now more thoroughly walk through them to consider the ones expanded already and automatically expand the remaining ones with either the types found on the user repository interface or the unresolved type variable.
Ticket: GH-3074.
…ort extensions.
Spring Data modules might override, and, by that, fix some of the generic type parameters exposed by RepositoryFactoryBeanSupport. We now more thoroughly walk through them to consider the ones expanded already and automatically expand the remaining ones with either the types found on the user repository interface or the unresolved type variable.
Ticket: GH-3074.
We could expand the type information that we expose via
BeanDefinition.setTargetType(…)
by inspecting domain and identifier type from theRepositoryMetadata
. This is in response to setting that type blessed by the fix for spring-projects/spring-framework#32489.The text was updated successfully, but these errors were encountered: