HttpMessageConverter should accept Class<? extends T> on can read [SPR-6771]

[spring-projects-issues]

Oliver Drotbohm opened SPR-6771 and commented

There's a small glitch similar to #11408 inside HttpMessageConverter. If you use it programatically you usually ask canRead(Class<? extends T> clazz, MediaType mediatype) before invoking read(Class<T> clazz, HttpInputMessage message). If you now have an implementation fixing generics to Object to be as general as possible you can call canRead with a Foo.class but then in turn not read with Foo.class as it is not compatible to Class<Object>.

---

Issue Links:

• HttpMessageConverter read and write methods have restrictive type annotations [SPR-6848] #11514 HttpMessageConverter read and write methods have restrictive type annotations

Referenced from: commits f2fdf9f

[spring-projects-issues]

Arjen Poutsma commented

I've changed the canRead/canWrite signatures to Class<?> instead of Class<? extends T>.