This repository was archived by the owner on Feb 23, 2023. It is now read-only.
Spring Data Repository with unresolved generics cannot be injected anymore #1324
Comments
snicoll
added a commit
that referenced
this issue
Dec 1, 2021
With gh-1292, we've stopped writing a resolvable type if it has unresolved generics. This broke Spring Data repository support as a repository may have such a signature and the context is not able to locate the type if the target type is not set. This is a workaround that provide a way to opt-in for such a type even if it has unresolved generics. See gh-1324
|
Closed by 82dac3f |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Regression reported by @christophstrobl.
What we've done in #1292 means that we will remove the generic type of a bean definition that has unresolved generics.
Consider the following repository:
Because the target entity is a
Something<?>we do remove the generics and this preventsSomethingRepositoryto be found as a candidate bean. We should fix that problem, which may require change in Spring Data but for now we will add a workaround for that specific use case.The text was updated successfully, but these errors were encountered: