Databases
StackOverflow2013
Postsdbo
POData binding of @ModelAttribute annotated parameters
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POData binding of @ModelAttribute annotated parameters
    primarykey
    data
    text
    <p>I have a Spring 2.5 annotated Controller in which I have a method annotated with @RequestMapping(method=RequestMethod.GET), which performs some logic to fill the model.</p> <p>I also have a method annotated with @RequestMapping(method=RequestMethod.POST) which performs the request. This method has a @ModelAttribute annotated parameter that contains my own form pojo, let's call it MyForm. I also have an initialization method for MyForm, also annotated with @ModelAttrribute. Now so far all works as expected: on a POST request the form data binds to MyForm and I can process it.</p> <p>The problem is that I want to be able to pre-populate the form by passing in (GET) request parameters. Since I have the @ModelAttribute method for MyForm, I do get a MyForm instance in my model, but it doesn't get populated unless I specifically use it as a parameter for my GET method.</p> <p>Why do I have to do this, is it possible to force data binding on my form for a GET request in a different way? I now just pass in the parameter, but because it is already in the model I don't have to do anything with it, resulting in an ugly unused method parameter.</p> <p>[Edit: some code examples to illustrate]</p> <p>The controller that doesn't populate the form on a get request:</p> <pre><code>@Controller public class MyController { @ModelAttribute("myForm") public MyForm createForm() { return new MyForm(); } @RequestMapping(method=RequestMethod.GET) public void handlePage(Model model) { //Do some stuff to populate the model.... } @RequestMapping(method=RequestMethod.POST) public void processForm(@ModelAttribute("myForm") MyForm myForm) { //Process the form } } </code></pre> <p>When I change the method signature of the handlePage method, it gets populated on a get request...</p> <pre><code>@RequestMapping(method=RequestMethod.GET) public void handlePage(Model model, @ModelAttribute("myForm") MyForm myForm) { //Do some stuff to populate the model.... } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJaap Coomans
    1. USJaap Coomans
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POData binding of @ModelAttribute annotated parameters
      1. USMike
      1. VTFavorite
    2. VO
      singulars
      1. POData binding of @ModelAttribute annotated parameters
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POData binding of @ModelAttribute annotated parameters
      1. USjbindel
      1. VTFavorite
    1. COWhen you say you have your own form pojo, you mean just some domain object, right? (as opposed to some custom spring form implementation.) Also is your view just a standard JSP?
      singulars
      1. POData binding of @ModelAttribute annotated parameters
      1. USAlex Beardsley
    2. COYep, you're right. Just some domain object. My view is not a JSP, but I'll spare you the details of the view implementation (not my own), because I can write a book about that alone...
      singulars
      1. POData binding of @ModelAttribute annotated parameters
      1. USJaap Coomans
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload