代码之家  ›  专栏  ›  技术社区  ›  Al Grant

为什么控制器需要在绑定错误上添加模型

  •  1
  • Al Grant  · 技术社区  · 7 年前

    例如我经常看到的 tutorials

        @PostMapping
    public String registerUserAccount(@ModelAttribute("user") @Valid UserRegistrationDto userDto, 
                                      BindingResult result){
    
        User existing = userService.findByEmail(userDto.getEmail());
        if (existing != null){
            result.rejectValue("email", null, "There is already an account registered with that email");
        }
    
        if (result.hasErrors()){
            return "registration";
        }
    
        userService.save(userDto);
        return "redirect:/registration?success";
    }
    

    我的控制器非常相似:

        @PostMapping("/user/register")
    public String registerNewUser(@ModelAttribute("user") @Valid RegisterUserDTO registerUserDTO,
                                  BindingResult bindingResult,
                                  Model model,
                                  HttpServletRequest request,
                                  Errors errors) {
        User existing = userService.findUserByEmail(registerUserDTO.getEmail());
        if (existing != null) {
            bindingResult.rejectValue("email", null, "There is already an account with that Email");
        }
        if (bindingResult.hasErrors()) {
            return "register";
        }
        userService.createUser(registerUserDTO);
        return "redirect:/registration?success";
     }
    }
    

    但是,当我返回“register”时,在与对象相关的第一个thymeleaf标记对应的堆栈上有一个绑定错误。

    如果我更改POST控制器以显式添加模型:

            if (bindingResult.hasErrors()) {
            model.addAttribute(registerUserDTO);
            return "register";
        }
    

    然后它工作,返回带有模型和先前输入的数据的页面。

    更新

    这也不起作用:

        @PostMapping("/user/register")
    public String registerNewUser(@ModelAttribute("user") @Valid RegisterUserDTO registerUserDTO,
                                  BindingResult bindingResult) {
        User existing = userService.findUserByEmail(registerUserDTO.getEmail());
        if (existing != null) {
            bindingResult.rejectValue("email", null, "There is already an account with that Email");
        }
        if (bindingResult.hasErrors()) {
            return "register";
    
    1 回复  |  直到 7 年前
        1
  •  0
  •   Al Grant    7 年前

    这起作用了:

        @PostMapping("/user/register")
        public String registerNewUser(@ModelAttribute("registerUserDTO") @Valid RegisterUserDTO registerUserDTO,
                                  BindingResult bindingResult) {
        User existing = userService.findUserByEmail(registerUserDTO.getEmail());
        if (existing != null) {
               bindingResult.rejectValue("email", null, "There is already an account with that Email");
        }
        if (bindingResult.hasErrors()) {
            return "register";
        }
        userService.createUser(registerUserDTO);
        return "redirect:/registration?success";
    }
    

    正如M.Denium指出的,@ModelAttribute名称需要与GET控制器中使用的支持对象的实例名称相同。在我的GET控制器中我有:

        @GetMapping("/user/register")
    String registerForm(Model model) {
        RegisterUserDTO registerUserDTO = new RegisterUserDTO();
        model.addAttribute(registerUserDTO);
        return "register";
    }
    

    寄存器SERDTO ")