Validation error responses in Spring Boot - Step-by-Step Execution

Concept Flow - Validation error responses

Client sends request with data

↓

Spring Boot validates data

↓

Data valid

↓

Process request

↓

Send success

↓

Client receives response

The client sends data, Spring Boot checks it, then either processes it or sends back validation errors.

Execution Sample

Spring Boot

@PostMapping("/users")
public ResponseEntity<?> createUser(@Valid @RequestBody User user, BindingResult result) {
  if (result.hasErrors()) {
    return ResponseEntity.badRequest().body(result.getAllErrors());
  }
  return ResponseEntity.ok(userService.save(user));
}

This code checks if user data is valid and returns errors if not, or saves the user if valid.

Execution Table

Step	Action	Validation Result	Branch Taken	Response Sent
1	Receive POST /users with user data	Not checked yet	N/A	N/A
2	Validate user data	Valid	No errors branch	Proceed to save user
3	Save user data	N/A	N/A	200 OK with saved user
4	Receive POST /users with invalid user data	Invalid	Has errors branch	400 Bad Request with error list
5	Return validation errors	N/A	N/A	400 Bad Request with error list

💡 Execution stops after sending either success or error response.

Variable Tracker

Variable	Start	After Validation	After Branch	Final
user	null	User object from request	Same	Same
result.hasErrors()	false	false or true depending on data	Checked	Used to decide response
response	null	null	Set to 200 OK or 400 Bad Request	Sent to client

Key Moments - 2 Insights

Why do we check result.hasErrors() before saving the user?

Because if validation fails, we must not save invalid data. The execution_table rows 2 and 4 show the branch decision based on validation.

What does the response contain when validation fails?

It contains a 400 Bad Request status and a list of validation error messages, as shown in execution_table rows 4 and 5.

Visual Quiz - 3 Questions

Look at the execution_table, what response is sent at step 3?

A 500 Internal Server Error

B 400 Bad Request with error list

C 200 OK with saved user

D No response sent

💡 Hint

Check the 'Response Sent' column at step 3 in the execution_table.

At which step does the validation detect invalid data?

A Step 4

B Step 1

C Step 2

D Step 5

💡 Hint

Look for 'Invalid' in the 'Validation Result' column in the execution_table.

If result.hasErrors() is false, what happens next?

A Return 400 Bad Request

B Save user and return 200 OK

C Throw exception

D Ignore request

💡 Hint

See the branch taken when validation is valid in execution_table step 2.

Concept Snapshot

Spring Boot validates incoming data automatically.
Use @Valid and BindingResult to check errors.
If errors exist, return 400 Bad Request with error details.
If no errors, process and return 200 OK.
This keeps data clean and user informed.

Full Transcript

When a client sends data to a Spring Boot server, the server checks if the data is valid using annotations like @Valid. The BindingResult object holds any validation errors. If errors exist, the server sends back a 400 Bad Request response with details about what was wrong. If the data is valid, the server processes it, such as saving a user, and sends back a 200 OK response with the saved data. This flow ensures only good data is saved and users get clear feedback on mistakes.