Consistent throwing of HttpMessageNotReadableException in HttpMessageConverter implementations [SPR-16995]

[spring-projects-issues]

Juergen Hoeller opened SPR-16995 and commented

Some HttpMessageConverter are inconsistent in their throwing of IOException versus HttpMessageNotReadableException, unnecessarily wrapping the former or throwing a mix of the latter and the general HttpMessageConversionException. Most importantly, ProtobufHttpMessageConverter needs a thorough revision here, as well as the JAXB2 based converters.

Let's streamline this for 5.1 and backport it to 5.0.8 as far as feasible.

---

Affects: 5.0.7

Issue Links:

• Read large data using InputStreamResource at ResourceHttpMessageConverter [SPR-13443] #18023 Read large data using InputStreamResource at ResourceHttpMessageConverter
• HttpMessageConverterExtractor should wrap HttpMessageNotReadableException in RestClientExceptions [SPR-13592] #18170 HttpMessageConverterExtractor should wrap HttpMessageNotReadableException in RestClientExceptions
• Pass input message to HttpMessageNotReadableException for better logging [SPR-15588] #20147 Pass input message to HttpMessageNotReadableException for better logging

Referenced from: commits ac1e287, d08b72a