Скачать или смотреть Stop Bad Input in Spring Boot (Jakarta Validation)

Your Spring Boot API might be wide open—if you skip input validation. In this video I show Bean/Jakarta Validation (Hibernate Validator) patterns that harden fields against bad data and common attacks. You’ll see the exact annotations I use in production: money, quantity, unit price, discount %, dates, pagination, phone (E.164), SKU, lists, titles, and enums.

What you’ll learn
Add Bean/Jakarta Validation to Spring Boot endpoints
Choose the right constraints (@DecimalMin, @Digits, @Positive, @FutureOrPresent, @Pattern, @Size, @NotBlank, @Max)
Replace string “status” with type-safe enums
Prevent common API bugs and tighten security

// TIMESTAMPS
00:00 Why is input validation important for APIs? (Intro)
00:12 How to validate money fields in Spring Boot? (@DecimalMin + @Digits)
  → How do you verify money values?
  → What is the valid currency format?
00:28 How to ensure quantity is positive? (@Positive)
  → How to make sure a number is positive in Java?
  → How do you validate a positive integer in Java?
00:38 How to validate unit price? (@DecimalMin + @Digits)
00:48 How to validate discount percentage? (@DecimalMin + @DecimalMax)
00:58 How to restrict delivery date to future? (@FutureOrPresent)
01:08 How to validate pagination params? (@PositiveOrZero, @Positive, @Max)
01:20 How to validate phone number (E.164 format)? (@Pattern)
01:30 How to validate SKU format? (@Pattern)
01:40 How to ensure lists are not empty? (@Size + @NotNull)
01:50 How to validate title length and non-blank? (@NotBlank + @Size)
02:00 Why use enums instead of strings for status?

#SpringBoot #HibernateValidator #BeanValidation #JakartaValidation #JavaDevelopers #APISecurity