Databases
StackOverflow2013
Postsdbo
POSpringMVC controller: how to stay on page if form validation error occurs
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSpringMVC controller: how to stay on page if form validation error occurs
    primarykey
    data
    text
    <p>I have next working code in my <em>SpringMVC</em> controller:</p> <pre><code>@RequestMapping(value = "/register", method = RequestMethod.GET) public void registerForm(Model model) { model.addAttribute("registerInfo", new UserRegistrationForm()); } @RequestMapping(value = "/reg", method = RequestMethod.POST) public String create( @Valid @ModelAttribute("registerInfo") UserRegistrationForm userRegistrationForm, BindingResult result) { if (result.hasErrors()) { return "register"; } userService.addUser(userRegistrationForm); return "redirect:/"; } </code></pre> <p>In short <code>create</code> method try to validate <code>UserRegistrationForm</code>. If form has errors, it leaves user on the same page with filled form fields where error message will be shown.</p> <p>Now I need to apply the same behaviour to another page, but here I have a problem:</p> <pre><code>@RequestMapping(value = "/buy/{buyId}", method = RequestMethod.GET) public String buyGet(HttpServletRequest request, Model model, @PathVariable long buyId) { model.addAttribute("buyForm", new BuyForm()); return "/buy"; } @RequestMapping(value = "/buy/{buyId}", method = RequestMethod.POST) public String buyPost(@PathVariable long buyId, @Valid @ModelAttribute("buyForm") BuyForm buyForm, BindingResult result) { if (result.hasErrors()) { return "/buy/" + buyId; } buyForm.setId(buyId); buyService.buy(buyForm); return "redirect:/show/" + buyId; } </code></pre> <p>I faced with issue of dynamic url. Now if form has errors I should specify the same page template to stay on current page, but also I should pass <code>buyId</code> as a path variable. Where are a conflict in this two requirements. If I leave this code as is, I get an error (I'm using <em>Thymeleaf</em> as a template processor):</p> <pre><code>Error resolving template "/buy/3", template might not exist or might not be accessible by any of the configured Template Resolvers </code></pre> <p>I can write something like <code>return "redirect:/buy/" + buyId</code>, but in this case I lose all data and errors of form object.</p> <p>What should I do to implement in <code>buyPost</code> method the same behaviour as in <code>create</code> method?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMaxim Kolesnikov
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSpringMVC controller: how to stay on page if form validation error occurs
      1. USHippoom
      1. VTFavorite
    1. COHave a look at http://stackoverflow.com/questions/18039064/spring-mvc-prg-passing-values-to-other-operation/18039981#18039981, you could use FlashAttributes to pass data to the redirected view.
      singulars
      1. POSpringMVC controller: how to stay on page if form validation error occurs
      1. USHippoom
    2. COThis solution is better than just redirect, because values of form's fields are saved. But in this case I loose my `BindingResult` for this form, so I still can't show validation errors to user after form submit.
      singulars
      1. POSpringMVC controller: how to stay on page if form validation error occurs
      1. USMaxim Kolesnikov
    3. COYou could pass BindingResult along with other data, see http://stackoverflow.com/questions/2543797/spring-redirect-after-post-even-with-validation-errors
      singulars
      1. POSpringMVC controller: how to stay on page if form validation error occurs
      1. USHippoom
 

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