This article analyzes a Spring MVC issue where a batch template download failed due to missing configuration, explores how @ResponseBody interacts with manual stream writes, presents code examples, debugging insights, and offers best‑practice recommendations for reliable file‑download endpoints.
This article explains the differences between @RestController and @Controller, shows how @RestController combines @Controller with @ResponseBody, and details the internal processing flow of the @ResponseBody annotation within Spring MVC's handler adapters and return‑value handlers.
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.
This article walks through the Spring MVC internals, explaining how the @ResponseBody annotation triggers JSON serialization by tracing the DispatcherServlet, HandlerAdapters, and ReturnValueHandlers, and includes runnable Spring Boot test code to illustrate the processing flow.
This article explains how Spring MVC uses @RequestBody to deserialize JSON request bodies into Java objects and @ResponseBody to serialize Java objects back to JSON, providing clear code examples, curl testing, and notes on @RestController behavior.
