> For the complete documentation index, see [llms.txt](https://www.pranaypourkar.co.in/the-programmers-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pranaypourkar.co.in/the-programmers-guide/java/java-concepts/specifications-and-standards/jsr/jsr-303-349-380-bean-validation.md).
# JSR 303, 349, 380 (Bean Validation)
## About
**Bean Validation** is a Java specification that defines a **standard way to declare and validate constraints** on object fields, method parameters, and return values using annotations. It plays a key role in **Java SE and EE** applications by helping enforce data integrity and input validation in a declarative and reusable way.
Bean Validation is defined through a series of JSRs:
* **JSR 303 – Bean Validation 1.0**
* **JSR 349 – Bean Validation 1.1**
* **JSR 380 – Bean Validation 2.0**
## **Why Use Bean Validation?**
* **Declarative Constraints**: Use annotations like `@NotNull`, `@Size`, `@Email` to enforce validation rules.
* **Reusability**: Write constraint logic once and apply it consistently across layers.
* **Integration**: Automatically integrated with Java frameworks like:
* **Spring Boot**
* **Jakarta EE (formerly Java EE)** (e.g., JAX-RS, JPA, CDI)
* **Hibernate (via Hibernate Validator)**
* **Interoperability**: Works uniformly across tools and platforms due to standardization.
## **JSR Evolution Timeline**
### **JSR 303: Bean Validation 1.0**
* **Released**: 2009
* **Purpose**: Introduced the foundational API for validation using annotations.
* **Main Features**:
* Field-level constraint annotations
* Custom constraint support
* Integration with JPA and POJOs
* **Examples**:
```java
public class User {
@NotNull
@Size(min = 5, max = 15)
private String username;
}
```
### **JSR 349: Bean Validation 1.1**
* **Released**: 2013
* **Enhancements**:
* **Method and constructor validation**
* **Cross-parameter constraint validation**
* Support for dependency injection containers (CDI, Spring)
* **Example**:
```java
public class UserService {
public void registerUser(@NotNull User user) {
// Automatically validated
}
}
```
### **JSR 380: Bean Validation 2.0**
* **Released**: 2017
* **Target Platform**: Java SE 8+
* **Major Improvements**:
* Support for Java 8 features:
* `Optional`, `java.time` types
* **Repeatable annotations**
* **Type use annotations** (container element validation)
* New built-in constraints:
* `@NotEmpty`, `@NotBlank`, `@Positive`, `@Negative`, etc.
* **Example (with container validation)**:
```java
public class ShoppingCart {
@NotEmpty
private List<@NotNull @Size(min = 2) String> items;
}
```
## **Summary Table of Bean Validation JSRs**
JSR
Version
Released
Key Enhancements
303
1.0
2009
Basic annotation validation on fields
349
1.1
2013
Method/constructor validation, CDI
380
2.0
2017
Java 8 support, container validation, more annotations
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://www.pranaypourkar.co.in/the-programmers-guide/java/java-concepts/specifications-and-standards/jsr/jsr-303-349-380-bean-validation.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.