0 views collected around this technical thread.
This article demonstrates how to implement multi‑version REST APIs in Spring Boot 3 by leveraging @RequestMapping attributes such as headers, params, and consumes, providing complete code examples, request screenshots, and a custom HttpMessageConverter for Content‑Type based versioning.
This article explains the JSONP technique, demonstrates how to implement it in Spring Boot with a simple REST endpoint, custom JSONP wrapper, ResponseBodyAdvice, and a customized HttpMessageConverter, and shows how to test the solution using HTML script tags.
This guide explains why and how to create a custom HttpMessageConverter in Spring Boot 2.7.12, covering the implementation of the converter, its registration in the MVC configuration, testing with Postman, and the underlying request‑response processing mechanism.
This article demonstrates how to create a custom HttpMessageConverter in Spring Boot 2.6.12 to parse a simple “name:张三,age:20” string into a Users object, configure it in WebMvc, and explains the underlying Spring MVC request‑handling flow that invokes the converter.
This guide explains how to implement a custom HttpMessageConverter in Spring Boot 2.5, covering the converter class, configuration, data model, controller, testing steps, and the internal request‑handling flow within the Spring MVC framework.
This article explains Spring Boot's default JSON response, the internal HttpMessageConverter selection process, and how to configure XML and custom YAML responses by adding Jackson dependencies and implementing a custom HttpMessageConverter.
In Spring MVC, the default data format returned by @ResponseBody depends on the client’s Accept header, and the framework selects an appropriate HttpMessageConverter through RequestResponseBodyMethodProcessor, which evaluates acceptable and producible media types to produce JSON, XML, or other formats.