Find JSRs
Submit this Search

Ad Banner

JSRs: Java Specification Requests
JSR 349: Bean Validation 1.1

Updates to the Original JSR

The following information has been added/updated to the original proposal:

2012.12.03: JSR 349 moved to JCP 2.9.

2.19 Please describe the communications channel you have established for the public to observe Expert Group deliberations, provide feedback, and view archives of all Expert Group communications.

Everything is detailed at

The schedule is available at

Details of the Expert Group nominations will be provided to be public using the beanvalidation-dev mailing list which is the same as the regular technical open mailing list.

2.20 What is the URL of the Issue Tracker that the public can read, and how does the public log issues in the Issue Tracker? which redirects to

2.21 Please provide the location of the publicly accessible document archive you have created for the Expert Group.

The various drafts are published at but the content will change once the specification is final.

The full specification archive is available at as a source code repository.

The EG communication archive is found at

Original Java Specification Request (JSR)

Identification | Request | Contributions | Additional Information

Section 1. Identification

Submitting Member: Red Hat middleware LLC

Name of Contact Person: Emmanuel Bernard

E-Mail Address:

Telephone Number: +33 6 66 47 80 86 / +33 1 41 91 23 23

Fax Number: +33 1 41 91 23 32

Specification Lead: Emmanuel Bernard

E-Mail Address:

Telephone Number: +33 6 66 47 80 86 / +33 1 41 91 23 23

Fax Number: +33 1 41 91 23 32

Initial Expert Group Membership:

- Red Hat Middleware LLC - Gerhard Petracek - Juergen Hoeller (VMWare) - Sebastian Thomschke

Supporting this JSR:

- Antonio Goncalves - Gerhard Petracek - London Java Community - Dhanji R Prasanna - Juergen Hoeller (VMWare) - Sebastian Thomschke

Section 2: Request

2.1 Please describe the proposed Specification:

Bean Validation standardizes constraint definition, declaration and validation for the Java platform. Its first incarnation has been widely popular amongst the Java community in both SE and EE environments.

Being a version 1.0, Bean Validation stayed on the conservative side feature wise. The community has expressed interest in additional features to enhance the work done in the first version of the specification.

The work of the Expert Group will be around the following main topics:

* Integration with other JSRs While not part of the Bean Validation specification per se, we want to pursue further collaborative work with some other JSR leads on how to integrate Bean Validation into the various lifecycles of the SE/EE platforms. The work we did with JPA 2 and JSF 2 showed that it is possible and beneficial for the platform and developers.
- JAX-RS: call Bean Validation upon HTTP method calls on parameters and return values.
- JAXB: some people have asked for integration between Bean Validation and JAXB. Basically, the Bean Validation constraints (at least the fundamental ones) could be converted into the XML schema descriptor (and vice versa) to guarantee a unified propagation between the Java land and the XML land.
- JPA: improve the integration by letting Bean Validation constraints influence the DDL generated with the constraints declared on the entity model.
- CDI: offer a way for Bean Validation pluggable components to allow CDI style injection (in particular constraint validator implementations).
- CDI: integrate method-level validation (see below).
- EJB: integrate method-level validation (see below) - eg. validation of parameters and results of EJB business method calls.
- JSF: In addition to property-level constraints class-level constraints should be supported, offer support for client side validation based on Java side constraints (offered today by some JSF libraries).

These are propositions and starting points that will be run by the various expert groups. Based on these discussions, the Bean Validation expert group will adjust or add new features to the core of the Bean Validation specification as deemed necessary to achieve a successful integration. The Bean Validation expert group will also try and achieve consistent validation declaration and usage across the various specifications it integrates with to ensure Java SE/EE coherence.

* Method level validation
Offer APIs to validate parameters and return values of method calls. These APIs would be used by any injection or AOP framework around method invocations. If a constraint violation is detected, an exception (eg. ConstraintViolationException) would be raised.

* @Valid and group propagation
Ability to translate a group into another group while cascading the validation. This can help reduce the number of groups and increase reuse.

* Constraint composition
Extend the model to support both AND and OR style composition

* Clarification of ambiguities found in Bean Validation 1.0

* Better alignment with modular environments

* Exclusion flag on @BigDecimal / @BigInteger: in Bean Validation 1.0, boundaries are included by default and it is not possible to declare a boundary as excluded from the valid values

* ConstraintViolationException builder

* Conversion from persistence storage exception to Bean Validation exception

* Validate an object graph assuming a list of changes to be applied

* Separate the notion of MessageResolver and MessageInterpolator

* Consider interpolating the invalid value in error messages

* Offer stereotypes to skip validation on empty or null

* Apply constraints on the elements of an iterator

* Add formatter syntax for interpolated messages

* Provide a way for accessing default implementations for XML configured bootstrap artifacts

* Programmatic API to declare constraints (as opposed to annotations today)

Note that this list is not exhaustive but gives a good representation. Additional feature requests are available in Bean Validation's issue tracker

The goal of the Expert Group will be to assess these issues, prioritize them as well as identify and pursue directions for enhancement of the overall programming model and facilities of Bean Validation.

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

The target platforms are Java EE and Java SE.

2.3 The Executive Committees would like to ensure JSR submitters think about how their proposed technology relates to all of the Java platform editions. Please provide details here for which platform editions are being targeted by this JSR, and how this JSR has considered the relationship with the other platform editions.

The Bean Validation API is designed for both Java EE and Java SE platform environments. It is proposed that Bean Validation 1.1 will be included as a required part of the Java Platform, Enterprise Edition version 7. Aligning the timeline of this JSR with that of Java EE 7 may therefore impact the scope of the Bean Validation 1.1 release. Features that may not be able to be addressed in Bean Validation 1.1 due to time constraints may become candidates for a future release.

2.4 Should this JSR be voted on by both Executive Committees?

No. It should be voted on by the Java SE / EE Executive Committee only.

2.5 What need of the Java community will be addressed by the proposed specification?

The goal of the proposed specification is to address the needs of the Java community by adding functionality to the Bean Validation API to address requests received from the members of the community and other JSR expert groups.

2.6 Why isn't this need met by existing specifications?

See 2.5 above. The Bean Validation 1.1 release will augment the Bean Validation API with features that have been requested by the community and that are not present in the current release.

2.7 Please give a short description of the underlying technology or technologies:

See above.

2.8 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

The API Specification will continue to use the javax.validation package and its subpackages.

2.9 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?


2.10 Are there any security issues that cannot be addressed by the current security model?


2.11 Are there any internationalization or localization issues?

Internationalization and localization is a feature of Bean Validation and no issue is expected at this stage.

2.12 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?


2.13 Please describe the anticipated schedule for the development of this specification.

July 2011 Expert Group formed
Q4 2011 Early Draft
Q1 2012 Public Review
Q3 2012 Final Release

2.14 Please describe the anticipated working model for the Expert Group working on developing this specification.

This specification will be developed in the open according to the Open Source philosophy. The primary means of communication will be via a public mailing list and conference calls if required. Face-to-face meetings will be scheduled if needed.

2.15 Provide detailed answers to the transparency checklist, making sure to include URLs as appropriate:

* The public can read the names of the people on the Expert Group.

Yes. This information will be available in all spec drafts and on the Update page of the JSR.

* The Expert Group business is regularly reported on a publicly readable alias.

We intend this to be the case. In addition, blogs ( will be used to keep the community updated on the progress of the JSR.

* The schedule for the JSR is publicly available, it's current, and I update it regularly.

This will be available via various updates in blog (

* The public can read/write to a wiki for my JSR.

No. Means of communication will be via:
- forums
- patch exchanges (GitHub pull requests)
- discussions on the issue tracker

* I read and respond to posts on the discussion board for my JSR on

The primary means of written interaction with the community will be via the Bean Validation forum already used during the development of JSR 303

* There is an issue-tracker for my JSR that the public can read.


* I have spoken at conferences and events about my JSR recently.

Yes. It is expected that expert group members will participate in conferences and events and present updates on Bean Validation 1.1

* I am using open-source processes for the development of the RI and/or TCK.

Yes. Both the Bean Validation RI and the Bean Validation TCK are developed under the Open Source Hibernate Validator project ( The source code is available at and .

* The Update tab for my JSR has links to and information about all public communication mechanisms and sites for the development of my JSR.

This will be the case.

2.16 Please describe how the RI and TCK will de delivered, i.e. as part of a profile or platform edition, or stand-alone, or both. Include version information for the profile or platform in your answer.

Red Hat Middleware LLC will deliver a Reference Implementation (RI) and Technology Compatibility Kit (TCK) available both stand-alone and as part of Java EE 7.

2.17 Please state the rationale if previous versions are available stand-alone and you are now proposing in 2.13 to only deliver RI and TCK as part of a profile or platform edition (See sections 1.1.5 and 1.1.6 of the JCP 2 document).


2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.

The specification will be licensed using the standard specification license or a more open license if times permit to develop one and fall into agreement with Oracle's legal team.
The RI and TCK will be licensed via the ASL 2.0 license.

Section 3: Contributions

3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

Bean Validation specification
Hibernate Validator (RI)

3.2 Explanation of how these items might be used as a starting point for the work.

Bean Validation as defined by JSR-303 will be the starting point for this work.

Experience with existing validation engines, vendor extensions and integration with other technologies (eg. presentation frameworks) to Bean Validation as defined by JSR-303 will be considered when evaluating new functionality.

Section 4: Additional Information (Optional)

4.1 This section contains any additional information that the submitting Member wishes to include in the JSR.

The expert group will be formed once the specification is approved. All expert group discussions will occur on an open list as described above, and anyone is welcome to join in with the discussion, you simply need to subscribe to the list.