Micronaut+Thymeleaf表单验证报错：ConstraintViolationException参数未指定

Let's break down what's causing your error and how to fix it step by step:

1. Fix the @Error Method Signature #

The error message Required argument [ConstraintViolationException constraintViolationException] not specified tells us Micronaut isn't properly injecting the exception into your error handler method. Make sure your method follows this structure:

import io.micronaut.http.HttpRequest;
import io.micronaut.http.annotation.Error;
import io.micronaut.views.ModelAndView;
import jakarta.validation.ConstraintViolation;
import jakarta.validation.ConstraintViolationException;
import java.util.List;
import java.util.stream.Collectors;

// This can be in your registration controller or a global @ControllerAdvice class
@Error(exception = ConstraintViolationException.class)
public ModelAndView handleValidationErrors(ConstraintViolationException exception, HttpRequest<?> request) {
    // Collect all validation error messages
    List<String> errorMessages = exception.getConstraintViolations()
            .stream()
            .map(ConstraintViolation::getMessage)
            .collect(Collectors.toList());

    // Pass errors and previous input back to the registration view
    return new ModelAndView("register", 
            java.util.Map.of("errors", errorMessages, "previousInput", request.getBody().orElse(null)));
}

Key points here:

• Include both ConstraintViolationException and HttpRequest<?> as parameters (Micronaut needs the request context to resolve the exception)
• Return a ModelAndView to explicitly tell Micronaut to render your Thymeleaf template instead of JSON

2. Verify Thymeleaf View Configuration #

Ensure your application.yml (or application.properties) has the correct settings to enable Thymeleaf and point to your template files:

micronaut:
  views:
    thymeleaf:
      enabled: true
      prefix: classpath:/templates/
      suffix: .html
      cache: false # Disable cache during development for easier testing

This ensures Micronaut prioritizes rendering Thymeleaf views over returning raw JSON when you return a ModelAndView.

3. Adjust Your Registration Controller Method #

Your main registration endpoint should return a view type (not a DTO) so Micronaut knows to use the view system. For example:

import io.micronaut.http.annotation.Body;
import io.micronaut.http.annotation.Controller;
import io.micronaut.http.annotation.Post;
import io.micronaut.views.ModelAndView;
import jakarta.validation.Valid;

@Controller("/auth")
public class AuthController {

    @Post("/register")
    public ModelAndView register(@Body @Valid UserRegistrationDto registration) {
        // Execute your registration logic here (save user to DB, etc.)
        // On success, redirect to login or home page
        return new ModelAndView("login");
    }

    // Add the @Error method from step 1 here (or in a global advice class)
}

Avoid returning a POJO/DTO directly here—stick to ModelAndView or a String (view name) to keep the view flow consistent.

4. Ensure Validation is Properly Enabled #

Double-check that you have the Micronaut validation dependency in your build file:
For Gradle:

implementation("io.micronaut.validation:micronaut-validation")

For Maven:

<dependency>
    <groupId>io.micronaut.validation</groupId>
    <artifactId>micronaut-validation</artifactId>
</dependency>

This dependency ensures Micronaut's validation system works correctly and throws ConstraintViolationException when @Valid fails.

Why Your Original Setup Failed #

The missing argument error happens because Micronaut couldn't resolve the ConstraintViolationException instance to pass to your @Error method. This usually stems from:

• Missing the HttpRequest<?> parameter in the error handler
• The error method being in a class that isn't recognized as a controller/advice component
• Incorrect view configuration causing Micronaut to default to JSON handling instead of view rendering

内容的提问来源于stack exchange，提问作者Kevin Tan