Validation error response formatting in Spring Boot - Step-by-Step Execution

Concept Flow - Validation error response formatting

Receive HTTP Request

↓

Validate Input Data

↓

Valid

↓

Process

↓

Send Success

↓

End

The server receives a request, checks input data validity, and either processes it or sends back a formatted error response.

Execution Sample

Spring Boot

public ResponseEntity<?> handleRequest(@Valid @RequestBody User user, BindingResult result) {
  if (result.hasErrors()) {
    return ResponseEntity.badRequest().body(formatErrors(result));
  }
  return ResponseEntity.ok("Success");
}

This code checks for validation errors and returns a formatted error response if any exist.

Execution Table

Step	Action	Validation Result	Response Created	Response Sent
1	Receive HTTP POST with User data	Not checked yet	No	No
2	Validate User fields (e.g. @NotNull, @Size)	Errors found: name is empty	No	No
3	Check if result.hasErrors()	True	Yes, formatErrors() creates error list	No
4	Return ResponseEntity.badRequest() with error body	N/A	Yes	Yes, error response sent
5	End request processing	N/A	N/A	N/A

💡 Validation errors detected, so error response is sent instead of success.

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
result.hasErrors()	false	true	true	true
errorResponseBody	null	null	[{"field":"name","message":"must not be empty"}]	[{"field":"name","message":"must not be empty"}]

Key Moments - 2 Insights

Why do we check result.hasErrors() before processing the request?

Because the execution_table row 3 shows that if validation errors exist, we must create and send an error response instead of continuing.

What does formatErrors(result) do?

It extracts field names and messages from validation errors to create a clear error list, as shown in variable_tracker for errorResponseBody.

Visual Quiz - 3 Questions

Look at the execution_table at step 2, what validation result is found?

A No errors found

B Errors found: name is empty

C Validation not performed yet

D All fields valid

💡 Hint

Check the 'Validation Result' column at step 2 in execution_table

At which step is the error response actually sent back to the client?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look at the 'Response Sent' column in execution_table

If the input had no validation errors, how would the execution_table change?

A Step 3 would show result.hasErrors() as false and no error response created

B Step 4 would still create an error response

C Step 2 would show errors found

D Step 5 would be skipped

💡 Hint

Refer to variable_tracker and execution_table rows about result.hasErrors()

Concept Snapshot

In Spring Boot, use @Valid and BindingResult to check input validation.
If errors exist, use BindingResult.hasErrors() to detect them.
Format errors into a clear response body.
Return ResponseEntity.badRequest() with error details.
Otherwise, proceed with normal processing and return success.

Full Transcript

When a Spring Boot controller receives a request with input data, it validates the data using annotations like @NotNull or @Size. The BindingResult object holds any validation errors. The code checks if result.hasErrors() is true. If yes, it formats these errors into a list showing which fields failed and why. Then it returns a bad request response with this error list as the body. If no errors are found, it processes the request normally and returns a success response. This flow ensures clients get clear feedback on what input was wrong.