Emmanuel Bernard recently sent an email to the JSR 303 Experts Group about the next revision of the Bean Validation JSR (303). Rather than sending the proposed changes privately, he blogged about them. I left a comment with what I'd like to see:
+1 for Client-side validation. I'd love to see an API that web frameworks can hook into to add "required" to their tags for HTML5. Or some service that can be registered so the client can make Ajax requests to an API to see if an object is valid.
Emmanuel replied that most of the necessary API already exists for this, but frameworks have been slow to adopt it.
The sad thing is that the API is present on the Bean Validation side but presentation frameworks are slow to adopt it and use it :(
RichFaces 4 now has support for it but I wished more presentation frameworks had worked on the integration. If you can convince a few people or have access to a few people, feel free to send them by me :)
The integration API is described here. Let me know if you think some parts are missing or should be improved. We should definitely do some more buzz around it.
In the interest of generating more buzz around it, I decided to do some research and see what JVM Frameworks support JSR 303. Here's what I've come up with so far (in no particular order):
- RichFaces 4 - Client Side Validation
- Tapestry's JSR 303 - Bean Validation Library
- Wicket JSR-303 Validators
- Configuring a JSR-303 Validator for use by Spring MVC
- GWT Validation
- Vaadin Bean Validation JSR 303 support
- Inline field validation in Scala/Lift using JPA and JSR 303