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
In the course of #19490, it turns out that GsonHttpMessageConverter should be sharing AbstractJackson2HttpMessageConverter's recently revised generic type handling, also shared by the new JsonbHttpMessageConverter.
The full extent of this is only really feasible in 5.0, but in particular deprecations of getTypeToken and co should be backported to 4.3.8 as well.
There's also the same generic type resolution algorithm in Jackson2CodecSupport in our new reactive codec abstraction. This needs to be unified and reused as far as possible.
Juergen Hoeller opened SPR-15381 and commented
In the course of #19490, it turns out that
GsonHttpMessageConverter
should be sharingAbstractJackson2HttpMessageConverter
's recently revised generic type handling, also shared by the newJsonbHttpMessageConverter
.The full extent of this is only really feasible in 5.0, but in particular deprecations of
getTypeToken
and co should be backported to 4.3.8 as well.Issue Links:
Referenced from: commits 3c8fc46, e5fdd4c
The text was updated successfully, but these errors were encountered: