Alexey Zvolinskiy

About Alexey Zvolinskiy

Alexey is a test developer with solid experience in automation of web-applications using Java, TestNG and Selenium. He is so much into QA that even after work he provides training courses for junior QA engineers.

Spring MVC: form handling vol. 1

Spring MVC is a part of Spring Framework and its main purpose is to make web-development more simple, convenient and easy. interaction with forms is a part of every more or less modern web application. Spring MVC allows you to perform all kinds of activity with forms in a very strict and simple way. In the article you will read the basics of form handling with the help of Spring MVC.

I will use one of my previous tutorials related to Spring MVC as a basis for the example below. I prefer java based configuration, so don’t be surprised that in this tutorial you will also see them. Let’s move to the section where I will point out the main aim of this post.

Spring form handling tutorials:

Main goal

I will show you how to handle form with the help of Spring MVC, how to bound a domain model with a form, how to process the form data and represent it in a view.


Our project will be based on Dynamic Web Project and Maven. It’s a traditional set which I recommend to use for a professional software development. The first steps will refer to the post mentioned earlier in the article. I mean the creation of the project in Eclipse and its conversion into Maven project. Further I will demonstrate you all required files which I need to complete the example.

pom.xml looks like:

<project xmlns="" xmlns:xsi="" xsi:schemalocation="">


		<!-- Spring -->
		<!-- CGLIB is required to process @Configuration classes -->
		<!-- Servlet API, JSTL -->



After all dependencies were declared we can proceed to the project configuration. As I mentioned before, I’m going to use annotation based config or as many people like to call it “a programmatic configuration approach”. It’s very convenient in case you want to avoid much of xml coding.

package com.sprmvc.init;

import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.ComponentScan;
import org.springframework.context.annotation.Configuration;
import org.springframework.web.servlet.config.annotation.EnableWebMvc;
import org.springframework.web.servlet.view.JstlView;
import org.springframework.web.servlet.view.UrlBasedViewResolver;

public class WebAppConfig {

	public UrlBasedViewResolver setupViewResolver() {
		UrlBasedViewResolver resolver = new UrlBasedViewResolver();
		return resolver;

package com.sprmvc.init;

import javax.servlet.ServletContext;
import javax.servlet.ServletException;
import javax.servlet.ServletRegistration.Dynamic;

import org.springframework.web.WebApplicationInitializer;
import org.springframework.web.servlet.DispatcherServlet;

public class Initializer implements WebApplicationInitializer {

	public void onStartup(ServletContext servletContext) throws ServletException {

		AnnotationConfigWebApplicationContext ctx = new AnnotationConfigWebApplicationContext();


		Dynamic servlet = servletContext.addServlet("dispatcher", new DispatcherServlet(ctx));


Next I’m going to create a class which will represent a data model bounded with the web form. It’s an important step because in the example I will use not simple html form tags but Spring form tag library.

package com.sprmvc.bean;

public class Person {

	private String firstName;
	private Integer age;

	public String getFirstName() {
		return firstName;

	public void setFirstName(String firstName) {
		this.firstName = firstName;

	public Integer getAge() {
		return age;

	public void setAge(Integer age) {
		this.age = age;

Notice that the Person class contains just fields with private access modificators and getters / setters for each field. Getters / setters are required because Spring form tags use them to interact with object fields in the view layer. The main part of the tutorial implies development of the controller and views. So let’s proceed.

package com.sprmvc.controller;

import org.springframework.stereotype.Controller;
import org.springframework.web.bind.annotation.ModelAttribute;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.servlet.ModelAndView;

import com.sprmvc.bean.Person;

public class PersonController {

	public ModelAndView personPage() {
		return new ModelAndView("person-page", "person-entity", new Person());

	public ModelAndView processPerson(@ModelAttribute Person person) {
		ModelAndView modelAndView = new ModelAndView();

		modelAndView.addObject("pers", person);

		return modelAndView;

The first method in the controller personPage() is responsible for navigation to the page with the form. Notice that return of the method contains Person() class. It’s required for the correct binding of the form with the domain model.
Now let’s move on to the overview of the Person Form page:

<%@ page language="java" contentType="text/html; charset=ISO-8859-1"
<%@taglib uri="" prefix="form"%>
<h1>Person page</h1>
<p>This is Person page</p>
<form:form method="POST" commandname="person-entity" action="process-person.html">
        <td><form:label path="firstName">Name:</form:label></td>
        <td><form:input path="firstName"></form:input></td>
        <td><form:label path="age">Age:</form:label></td>
        <td><form:input path="age"></form:input></td>
        <td colspan="2">
            <input value="Submit" type="submit">

Here I want to highlight two valuable moments. The first is the import of the spring form tag library. The second is the parameter commandName=”person-entity”. Its value equals to the value of the return parameter in the controller’s first method. Pay your attention that all labels in the form contain path values absolutely correspond to the Person class fields. Let’s go back to the second method processPerson(@ModelAttribute Person person). In this method I want to underline several moments:

  • The method gets parameter Person object annotated with @ModelAttribute. The annotation defines that the method’s argument (Person person) will refer to an appropriate attribute passed from the form.
  • @RequestMapping(value=”/process-person”) contains the value of the URL which will be processed by the method. The same value I have defined in the person-page.jsp; I mean the form’s attribute action=”process-person.html”.
  • I have specified the name of the person object which I pass to modelAndView object. The vname is “pers”. I will use this name in the to call parameters which I need.
<%@ page language="java" contentType="text/html; charset=ISO-8859-1"
<h1>Person Result page</h1>
<p>Student's name is ${pers.firstName}. The age is ${pers.age}.

Here everything is simple. I use an expression language to access all needed values of the person object which I get after the second method of the controller processes a request. As the result I get such project structure:


In this tutorial you have seen how to handle forms using Spring MVC. There are not all possible wayshow you can do it. In the future lessons I will demonstrate the rest variants of form handling. The result of the work you can see below:


You can download this project from my DropBox.

Reference: Spring MVC: form handling vol. 1 from our JCG partner Alexey Zvolinskiy at the Fruzenshtein’s notes blog.
Related Whitepaper:

Introduction to Web Applications Development

Kick start your web apps development with this introductory ebook!

This 376 page eBook 'Introduction to Web Applications Development', starts with an introduction to the internet, including a brief history of the TCT/IP protocol and World Wide Web. It defines the basic concepts for web servers and studies the case of Apache, the most used webserver, while other free software webservers are not forgotten. It continues with webpage design focusing on HTML and JavaScript. XML Schemas, their validation and transformation are covered as well as dynamic webpages built with CGI, PHP or JSP and database access.

Get it Now!  

One Response to "Spring MVC: form handling vol. 1"

  1. Omar Gameel Salem says:

    in the form attributes, you are using commandname which gives exception ‘Neither BindingResult nor plain target object for bean name ‘command’ available as request attribute’.

    instead you should use commandName (capital N)

Leave a Reply

nine − 1 =

Java Code Geeks and all content copyright © 2010-2014, Exelixis Media Ltd | Terms of Use | Privacy Policy
All trademarks and registered trademarks appearing on Java Code Geeks are the property of their respective owners.
Java is a trademark or registered trademark of Oracle Corporation in the United States and other countries.
Java Code Geeks is not connected to Oracle Corporation and is not sponsored by Oracle Corporation.

Sign up for our Newsletter

20,709 insiders are already enjoying weekly updates and complimentary whitepapers! Join them now to gain exclusive access to the latest news in the Java world, as well as insights about Android, Scala, Groovy and other related technologies.

As an extra bonus, by joining you will get our brand new e-books, published by Java Code Geeks and their JCG partners for your reading pleasure! Enter your info and stay on top of things,

  • Fresh trends
  • Cases and examples
  • Research and insights
  • Two complimentary e-books