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
GenericTypeResolver does not resolve nested generics - causes issues with Jackson & Spring MVC #31690
Comments
Thanks @quaff, I also assumed your work would fix this. However I don't think this is a duplicate as this used to work in 6.0.x and I'd like to understand why it broke. |
Hadn't really had time to look at this properly hence the poorly formatted test and believe line but it seems |
That's a bit embarrassing, but it looks like I shipped involuntarily a commit related to #22313 which is still opened while working on another issue, sorry about that. When I worked deeper on that issue, I found that by design Kotlin reflection is required to solve the Kotlin issue, and I was afraid of potential regressions on Java side, and chose to document the behavior via #31370. As a consequence, I plan to revert f075120. |
This reverts commit f075120. See spring-projectsgh-22313 See spring-projectsgh-31690
This reverts commit f075120. See spring-projectsgh-22313 See spring-projectsgh-31690
This affects spring 6.1.1
The following test passes on 6.0.14 but fails on 6.1.1
Failure message:
I believe this was caused by f075120
This causes nested generic deserialisation to fail from jackson due to the use of GenericTypeResolver in
org.springframework.http.converter.json.AbstractJackson2HttpMessageConverter.getJavaType(Type, Class<?>)
The text was updated successfully, but these errors were encountered: