Spring MVC form submit using modelAttribute

Question

I have something like

@RequestMapping("/showRegister")
public String showUserRegistrationForm(ModelMap modelMap) {
    modelMap.addAttribute("user", new UserBean());
    return "Register";
}

@RequestMapping("/RegisterUser")
public String registerUser(@ModelAttribute("user") UserBean userBean,
        BindingResult result, ModelMap modelMap) {
    System.out.println(userBean.getPassword());
    return "Register";
}

in my code.

The above works perfectly. Now suppose I want to save the modal data from form into multiple tables each having its own POJO Class. So how would the code be so as to receive not just UserBean as modelattribute but also other classes. Will I have to create a new POJO containing data from both the classes or is there a other way around.

EDIT

I read about DTO. But doesn't it make a repetition of POJO's. Can't we use a mix of 2-3 POJO's instead.

Take a look at Hibernate and other ORM frameworks. Or take a look at JDBC (and after Spring data) on how to persist objects to database. — Sotirios Delimanolis
– Sotirios Delimanolis, Commented Mar 26, 2013 at 19:36

Andres Olarte · Accepted Answer · 2013-03-26 19:42:40Z

1

You could create a "form" bean, and add your UserBean and any other pojos to it as members. I actually prefer to do this, since it makes complex validation easier and more self contained.

public class MyFormBean {

private UserBean userBean;
private MyOtherBean otherBean;

// Add getters and setters as needed

}

Then your form needs to reference the correct path to drill down into your object. If you had something like:

<form:input path="name" />

You would change it to

<form:input path="userBean.name" />

edited Mar 26, 2013 at 19:42

answered Mar 26, 2013 at 19:32

Andres Olarte

4,3803 gold badges27 silver badges46 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Akhil K Nambiar Over a year ago

how should i do that. what are the changes in here to be made.

Akhil K Nambiar Over a year ago

can you comment on DTO. any advantage for using it rather than form bean.

Andres Olarte Over a year ago

A DTO allows communication between different systems. My suggestion could be considered a DTO for a particular communication (between the View and the Controller). A DTO might be a completely new object with different representation of your existing data. This would work, but would be very hard to maintain. If you add a field in one place, you would need to add it to the other object. You avoid that with encapsulation.

Collectives™ on Stack Overflow

Spring MVC form submit using modelAttribute

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related