ViewResolver – Rendering Views

In Spring MVC, ViewResolver is the component responsible for rendering the final output that users see in their browser. Once the controller finishes processing a request, ViewResolver decides which view file should be used and how that view should be rendered.

In simple terms, the controller decides what data to show, while ViewResolver decides how that data is presented on the screen. This clear separation makes Spring MVC applications clean, flexible, and easy to maintain.

What Is ViewResolver?

ViewResolver is a core Spring MVC component that maps a logical view name returned by a controller to an actual view technology, such as JSP, Thymeleaf, or FreeMarker.

When a controller returns a view name like:

"home"
"userProfile"

Spring does not know which physical file to render.

The ViewResolver resolves this logical name into a real file path, for example:

/WEB-INF/views/home.jsp

or

templates/userProfile.html

Why ViewResolver Is Needed

Controllers should focus only on business logic, not on UI rendering details.

Without ViewResolver:

• Controllers would need to return full file paths
• Applications would become tightly coupled
• Changing the UI technology would require code changes

With ViewResolver:

• Controllers stay clean and reusable
• UI technologies can be changed easily
• Application becomes maintainable and scalable

Where ViewResolver Fits in the Spring MVC Flow

In Spring MVC, every HTTP request follows a well-defined lifecycle. ViewResolver plays its role only when a view needs to be rendered.

Spring MVC Request Flow

When ViewResolver Is Used

• If the controller returns a logical view name (for example, "home" or "userProfile"):
  • ViewResolver is invoked
  • It resolves the view name to a real template (JSP, Thymeleaf, FreeMarker)
  • The view is rendered and sent as HTML to the client

Example:

return"home";

When ViewResolver Is Skipped

• If the controller returns:
  • JSON
  • XML
  • ResponseEntity
  • Or uses @RestController / @ResponseBody

In this case:

• ViewResolver is NOT involved
• HttpMessageConverters serialize the response data
• The response is written directly to the HTTP body

Example:

return ResponseEntity.ok(user);

How ViewResolver Works

When a client sends a request, it flows through the DispatcherServlet and reaches the controller. After processing, the controller returns:

• A logical view name
• Along with model data

The DispatcherServlet then asks the ViewResolver to resolve the view name.

The ViewResolver:

1. Locates the correct view file
2. Merges model data into the view
3. Renders the final HTML
4. Sends the response back to the client

Simplified Flow

Client → DispatcherServlet → Controller → ViewResolver → View → Response

Example – ViewResolver in Action

Controller Code

@Controller
publicclassHomeController {

@GetMapping("/home")
public StringhomePage(Model model) {
        model.addAttribute("message","Welcome to Spring MVC");
return"home";
    }
}

What Happens Internally

• Controller returns "home" as the logical view name
• ViewResolver resolves it to:

  • /WEB-INF/views/home.jsp

    or

  • templates/home.html

• Model data is injected into the view
• Final HTML is rendered and sent to the browser

Common ViewResolver Implementations in Spring MVC

Spring MVC supports multiple view technologies, each with its own ViewResolver.

InternalResourceViewResolver

• Commonly used with JSP.
• It resolves logical view names to JSP files under a fixed directory.

Example:

home → /WEB-INF/views/home.jsp

ThymeleafViewResolver

Used with Thymeleaf templates, especially popular in Spring Boot applications.

Example:

profile → templates/profile.html

FreeMarkerViewResolver

• Used when FreeMarker is the chosen template engine.
• Often preferred for complex or dynamic UI rendering.

Example:

email → templates/email.ftl

BeanNameViewResolver

• Resolves views based on bean names defined in the Spring context.
• Less commonly used, but useful in advanced customization scenarios.

Why ViewResolver Is Important

ViewResolver provides several key benefits:

• Separates business logic from presentation logic
• Keeps controllers clean and focused
• Supports multiple view technologies
• Makes UI changes easier
• Improves maintainability and scalability

ViewResolver vs REST APIs in Spring MVC

Conclusion

ViewResolver is the rendering engine selector of Spring MVC. After the controller completes its work, ViewResolver takes over to locate the correct view, render it with model data, and send the final response to the client.

Together with DispatcherServlet, HandlerMapping, and HandlerAdapter, ViewResolver completes the Spring MVC request lifecycle, ensuring a clean, flexible, and professional architecture suitable for real-world applications.