The materials on this page are provided by the Spec Lead of this JSR
for evaluation and feedback.
These materials are not final, and are subject to change
as the JSR progresses through the process.
Latest News
To follow the news around Bean Validation, subscribe to the news feed on our homepage. New releases are also announced on Twitter by the spec lead at http://twitter.com/gunnarmorling
Contribution Guide
Bean Validation is run as an open source project. You can contribute to the API, the specification, the TCK and the reference implementation Hibernate Validator. Refer to the contribution guide on beanvalidation.org to learn more!
To get in touch with the Bean Validation expert group, send a mail to the beanvalidation-dev mailing list.
Transparency Checklist
Q: Is the schedule for the JSR publicly available, current, and updated regularly?
A: Yes. It is shown this JSR's page at jcp.org. Updates will be communicated on the blog http://beanvalidation.org/ if needed.
Q: Can the public read and/or write to a wiki for the JSR?
A: There will be public read/write access, but not via a wiki. Means of communication will be via:
Forum
Patch exchanges (GitHub pull requests)
discussions on the issue tracker
"Write" access will happen through the open issue tracker access as well as pull requests to the Bean Validation website
Q: Is there a publicly accessible discussion board for the JSR that you read and respond to regularly?
A: Yes. We will to continue to interact with the community via the Bean Validation forum already used during the development of JSR 303 and JSR 349 at https://forum.hibernate.org/viewforum.php?f=26
Q: Have you spoken at conferences and events about the JSR recently?
A: Bean Validation 2.0 has been presented at conferences including Devoxx US, JavaLand, jdk.io and RivieraDev. It is expected that expert group members will participate in conferences such as JavaOne and present updates on Bean Validation 2.0.
Q: Are you using open-source processes for the development of the RI and/or the TCK?
Q: What are the Terms of Use required to use the collaboration tools you have prepared to use with the Expert Group, so that prospective EG members can judge whether they are compatible with the JSPA?
A: For using the publicly available issue tracker, the terms of use described at http://www.atlassian.com/hosted/terms.jsp apply. For using the source code management system (e.g. to propose changes to the spec, the RI, the TCK or the beanvalidation.org website), the terms of use described at https://github.com/site/terms apply.
Q: What is the location of your publicly-accessible Issue list? In order to enable EC members to judge whether Issues have been adequately addressed, the list must make a clear distinction between Issues that are still open, Issues that have been deferred, and those that are closed, and must indicate the reason for any change of state.
Q: Which specific areas of feedback should interested community members (such as the Adopt-a-JSR program) provide to improve the JSR (please also post this to your Community tab)?
A: We are especially interested in real-world experiences with Bean Validation 1.0/1.1 as well as the proprietary support for Java 8 in the RI and any feature requests or suggestions by the community resulting from that.
