Search Tutorials

Spring MVC Tutorials | JavaInUse

Creating our first MVC program


Before we start writing our first Spring MVC program, lets understand how this is implemented in Spring.

Previously when using JSP Servlets, one had to configure a Servlet for each incoming request. In Spring MVC this is not the case, we do not have to configure any servlet. Spring MVC makes use of a pre-configured servlet called DispatcherServlet. We only make use of this DispatcherServlet to route the incoming request to the correct Controller and View and return it to the user.

Lets take an example. Here we will be designing an Employee Management System. Here the user requests to display all Employees information.
Here the User requests to show all the Employees information in the system. The client browser sends the request. This request is received by the DispatcherServlet. The DispatcherServlet then routes this request to the correct Controller, in this case the The does the actual process of retrieving the Employee info. After this it returns to the DispatcherServlet the Model Data which represents all the Employee info retrieved and the view details which will show this model data. The View name returned in our case is displayEmployees.jsp. The ServletDispatcher then routes this data to the ViewResolver. The ViewResolver then selects the correct View, populates it with the Model Data and returns it to DispatcherServlet. The DispatcherServlet then returns this populated View to the client.

Lets Begin

In the previous chapter we configured the Development Environment required for writing Spring MVC.
We will create Eclipse Maven project as follows-

We will have to add one more additional dependency to the pom.xml configured in the previous chapter. We add the jstl dependency required for displaying elements in the jsp page. So our pom will be-
<project xmlns="" xmlns:xsi=""
	<name>employee-management-system Maven Webapp</name>
Next we configure DispatcherServlet in web.xml.Here all the incoming request with .do extension will now be routed by the DispatcherServlet to the configured Controllers.-
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="" xmlns:xsi=""

	<!-- Configure the Disptcher Servlet -->
	<!-- Filter the incoming requests for the .do pattern -->

Next we will write Application Context to configure the beans. Spring MVC automatically loads a application context with the name- <servlet-name>-servlet.xml. So in our case Spring will automatically load the Application Context named as Dispatcher-servlet.xml.
In this configuration file we have written code to scan the packages com.javainuse.controller and "com.javainuse.service.
<beans xmlns=""
	xmlns:xsi="" xmlns:p=""
	xmlns:mvc="" xmlns:context=""

	<!-- Scan these packages for Annotated classes -->
	<context:component-scan base-package="com.javainuse.controller" />
	<context:component-scan base-package="com.javainuse.service" />
	<mvc:annotation-driven />
Now lets write our Java classes. First we write the Domain class
package com.javainuse.domain;

public class Employee {

	private String empId;
	private String name;
	private String designation;
	private double salary;

	public Employee() {

	public Employee(String empId, String name, String designation, double salary) {
		this.setEmpId(empId); = name;
		this.designation = designation;
		this.salary = salary;

	public String getName() {
		return name;

	public void setName(String name) { = name;

	public String getDesignation() {
		return designation;

	public void setDesignation(String designation) {
		this.designation = designation;

	public double getSalary() {
		return salary;

	public void setSalary(double salary) {
		this.salary = salary;

	public String getEmpId() {
		return empId;

	public void setEmpId(String empId) {
		this.empId = empId;

Next we write the controller. Above in the Dispatcher-context.xml we have context:component-scan base-package="com.javainuse.controller". So Spring scans this particular package for a class annotated with @Controller. The DisplayEmployeeController has a dependency of In DisplayEmployeeController we have a method viewAllItems which has been mapped to the URL /viewAllEmployees. In the xml configuration files we have configured the DispatcherServlet such that when the client hits the DispatcherServlet scans the package com.javainuse.controller looking for Controller. The DisplayEmployeeController returns ModelAndView containing the populated Model class Employee and the View name. Currently in our configurations we have not specified any ViewResolver. So by default Spring will use the default InternalResourceViewResolver. In the next chapters we will look at the other view resolvers.

We will write a class DisplayEmployeeController as follows-
package com.javainuse.controller;

import java.util.List;

import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.stereotype.Controller;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.servlet.ModelAndView;

import com.javainuse.domain.Employee;
import com.javainuse.service.EmployeeService;

public class DisplayEmployeeController {

	private EmployeeService employeeService;

	public ModelAndView viewAllItems() {
		List<Employee> allEmployees = employeeService.getAllEmployees();
		return new ModelAndView("/displayAllEmployees.jsp", "allEmployees",
In DisplayEmployeeController we have autowired EmployeeService class. Also in the Dispatcher-context.xml we have context:component-scan base-package="com.javainuse.service" Spring scans this particular package for a class annotated with @Component. The EmployeeService class will actually fetch all the required Employee information. Usually EmployeeService should call the EmployeeDAO which will return all items from the DataBase.But here we will mock the EmployeeService class to just return the list of items as follows. We are using the Programming to Interface concept here. You can read more about this in this chapter. So we create the and as follows.
package com.javainuse.service;

import java.util.List;

import com.javainuse.domain.Employee;

public interface EmployeeService {
	public List<Employee> getAllEmployees();

package com.javainuse.service;

import java.util.ArrayList;
import java.util.List;

import org.springframework.stereotype.Component;

import com.javainuse.domain.Employee;

public class EmployeeServiceMockImpl implements EmployeeService {

	private List<Employee> testEmployees = new ArrayList<Employee>();

	// populate the Employee List
	public EmployeeServiceMockImpl() {
		testEmployees.add(new Employee("1", "emp1", "M1", 10000));
		testEmployees.add(new Employee("2", "emp2", "M2", 20000));
		testEmployees.add(new Employee("3", "emp3", "M3", 30000));
		testEmployees.add(new Employee("4", "emp4", "M4", 40000));
		testEmployees.add(new Employee("5", "emp5", "M5", 50000));
		testEmployees.add(new Employee("6", "emp6", "M6", 60000));

	// Return the Mocked Employee List
	public List<Employee> getAllEmployees() {
		return new ArrayList<Employee>(testEmployees);
The DisplayEmployeeController returns the list of employees to a JSP page called displayAllEmployees.jsp using the following code statement
return new ModelAndView("/displayAllEmployees.jsp", "allEmployees", allEmployees);
We will write the displayAllEmployees JSP page to display the Employee List allEmployees as follows-
<%@ taglib uri="" prefix="c"%>
<%@ taglib prefix="fmt" uri=""%>
<%@ taglib prefix="fn" uri=""%>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Show Employees</title>
	<div id="books">
			<c:forEach items="" var="nextEmp">
We now run the two eclipse commands- clean install, tomcat:run to deploy the application. Now open a browser and hit the URL http://localhost:8080/employee-management-system/ We will see the Employee info as follows-

Download Source Code

Download it - Spring-MVC Project

What Next?

In the next chapter will implement Spring MVC: Add Employee Functionality without Spring Form Handling.