Spring MVC Configuration: XML vs Java-Based (Annotation) Approach

In Spring MVC, configuration is necessary to handle incoming web requests, resolve views and manage controllers. You can configure Spring MVC using either:

• XML-based configuration (traditional approach).
• Java-based configuration (modern, annotation-driven approach).

Both methods serve the same purpose, but the choice depends on the flexibility and maintainability requirements of the project.

XML-Based Configuration

XML-based configuration is the traditional way of configuring Spring applications. In this approach, beans such as controllers, view resolvers and other necessary components are declared in XML files. Though verbose, XML provides a clear and declarative approach, making it ideal for legacy systems.

How It Works:

1. DispatcherServlet is defined in web.xml, mapping requests to a specific URL pattern (e.g., /).

2. A separate XML file (often named dispatcher-servlet.xml) contains the bean definitions for:

• Controllers (@Controller classes).
• View Resolvers (such as InternalResourceViewResolver for JSPs).
• Any other Spring beans required by the application.

3. The web.xml file initializes the DispatcherServlet, which reads from the XML file to know how to handle requests.

Example: Creating XML-Based Spring MVC Configuration

Step 1: Create a New Maven Project

1. Open IntelliJ IDEA / Eclipse
2. Select New Project → Maven
3. Project details: Group Id: com.example, Artifact Id: spring-mvc-xml
4. Packaging: war
5. Finish project creation

Step 2: Add Required Dependencies (pom.xml)

Add required Spring MVC, Servlet API, and JSP support libraries. Add the following dependencies to pom.xml:

Explanation:

• spring-webmvc -> Core Spring MVC framework
• javax.servlet-api -> Required to run on Tomcat
• jstl -> Enables JSTL tags in JSP pages

Step 3: Configure DispatcherServlet (web.xml)

Create web.xml inside WEB-INF:

Explanation:

• DispatcherServlet receives all incoming requests
• / mapping means every request goes through Spring MVC
• It automatically loads spring-servlet.xml

Step 4: Create Spring MVC XML Configuration (spring-servlet.xml)

Create spring-servlet.xml inside WEB-INF:

Explanation:

• <mvc:annotation-driven /> -> Enables @Controller, @GetMapping
• <component-scan> -> Finds controller classes automatically
• InternalResourceViewResolver -> Maps view names to JSP files

Step 5: Create Controller Class

Create HomeController.java:

Explanation:

• @Controller -> Marks this as MVC controller
• @GetMapping("/") -> Handles root URL
• "home"-> Resolved to /WEB-INF/views/home.jsp
• addObject() -> Sends data to JSP

Step 6: Create JSP View

Create home.jsp inside /WEB-INF/views/:

Explanation:

• ${message} retrieves model data
• JSP renders final HTML response

Step 7: Configure Tomcat Server

• Download Apache Tomcat 9
• In IDE:
• Add Tomcat Server
• Deploy spring-mvc-xml project
• Start the server

Step 8: Run & Test Application

Open browser and hit:

http://localhost:8080/spring-mvc-xml/

Output:

Java-Based Configuration

Java-based configuration is a modern approach introduced in Spring 3.0, which eliminates the need for XML files by using annotations. With @Configuration, developers can configure Spring in plain Java classes, making the setup more concise and readable.

How It Works:

• @EnableWebMvc enables Spring MVC features, such as controller and request mapping.
• @ComponentScan is used to scan the base packages for annotated components like @Controller.
• @Configuration classes are used to configure components like view resolvers, data sources and more.
• DispatcherServlet can be registered programmatically using WebApplicationInitializer or AbstractAnnotationConfigDispatcherServletInitializer.

Example: Creating Java-Based Spring MVC Configuration

Step 1: Create a New Maven Project

1. Open IntelliJ IDEA / Eclipse
2. Select New Project -> Maven
3. Enter project details:
4. Group Id: com.example
5. Artifact Id: spring-mvc-java-config
6. Set Packaging: war
7. Click Finish to create the project

Step 2: Add Dependencies (pom.xml)

Add Spring MVC, Servlet API, and JSTL.

Explanation:

• spring-webmvc -> Core Spring MVC
• javax.servlet-api -> Provided by Tomcat
• jstl -> Used in JSP

Step 3: Create web.xml

Create web.xml inside WEB-INF.

Explanation:

• DispatcherServlet is the front controller
• / mapping sends all requests to Spring MVC

Step 4: Create Java Configuration Class

Create WebConfig.java.

Explanation:

• @Configuration -> Java config class
• @EnableWebMvc ->Enables Spring MVC features
• @ComponentScan -> Finds controllers

Step 5: Register Java Config with DispatcherServlet

Create a class extending AbstractAnnotationConfigDispatcherServletInitializer.

Explanation:

• Replaces XML-based servlet config
• Connects DispatcherServlet with WebConfig

Step 6: Create Controller Class

Create HomeController.java.

Explanation:

• @Controller -> Marks MVC controller
• @GetMapping("/") -> Handles root URL
• "home" -> JSP name
• addObject() -> Sends data to JSP

Step 7: Create JSP View

Create home.jsp inside /WEB-INF/views.

<html>
<head>
<title>Home</title>
</head>
<body>
<h1>${message}</h1>
</body>
</html>

Explanation:

• ${message} -> Reads model data
• JSP renders HTML response

Step 8: Deploy on Tomcat

• Deploy WAR file on Apache Tomcat.
• Spring MVC applications require a servlet container.

Step 9: Test the Application

Open browser:

http://localhost:8080/spring-mvc-java-config/

Output:

XML Config vs Java-based Config