Are you doing client-side validation in your JSF applications?
Are you doing client-side validation in your JSF application? I am in Equinox and AppFuse, but it seems somewhat primitive. I'm using David Geary's corejsf-validator.jar from his Core JSF book. It hooks into Commons Validator, and while it does work - it has some issues.
First of all, if you have it in your classpath when testing, it screws up Ant-style path matching in Spring (applicationContext*.xml doesn't work). Secondly, it puts all the JavaScript validation functions right in your page, rather than in an external file that can be cached by your browser.
In reality, I believe that JSF should include client-side validation as part of the spec. After all, all of the other popular Java web frameworks support it. Then again, Rails is growing in popularity and AFAIK, it doesn't support it. In addition, the popular Java webapps I've seen (JIRA, Confluence, Jive Forums) don't use it either. I'm not trying to advocate that we should all be using client-side validation in our apps, I'm merely saying it should be an option in the standard web framework for Java.
The only public (and open source) option I've found is the Commons Validator support in Shale. Will this work in a MyFaces application w/o Shale? Are there other client-validation frameworks for JSF I don't know about? Or is the best option "don't use client-side validation with JSF?"
Posted by 195.87.22.155 on December 15, 2005 at 01:25 PM MST #
Posted by Matt Raible on December 15, 2005 at 05:24 PM MST #
Posted by Ça?atay Çivici on December 19, 2005 at 12:31 PM MST #
Posted by Mert Caliskan on December 19, 2005 at 12:53 PM MST #
Posted by PrasannaKarthik.S on January 06, 2006 at 04:46 PM MST #
One of the features is client side validation. Some features:
1. The tool is completely configurable using annotations and XML.
2. Each generated form can function in either read-only or editable model, depending on the "editable" attribute.
3. The form uses configuration-by-exception for its field rendering for security
4. Forms may be referenced by Facelets tags to decrease application coupling.
5. Tool forces good practice for code management (different users same style)
6. Entity field property propagation to the form allows client-side validation
7. I provide two tag libraries with client-side validation and new input component types like Password, Link, Html, ColorPicker. (The first library is Seam+RichFaces, and the second library is simple JSF.)
8. I also created new field annotations like (password, link, html, javaScriptPattern, formOrder) for complete form generation.
9. Form creation and maintenance is completely handled by the tool. After entity bean updates, "fresh" forms are autogenerated to match.
More information is available here:
http://cs.ecs.baylor.edu/~cerny/formBuilder/guide.html
Currently, you can download FormBuilder from
http://cs.ecs.baylor.edu/~cerny/formBuilder/ download. Later I am planning to put it on SourceForge.net.
I welcome any feedback (even bad) on this work.
Seam community
(http://www.seamframework.org/Community/FormBuilderSeamgenExtensionAnnouncement).
Posted by Tomas Cerny on March 10, 2008 at 02:18 AM MDT #