J
johkar
Slightly off-topic I know, but I thought this might be the best group
to provide insight.
We have been using the Struts validator (server-side) successfully for
both page level and field level errors in J2EE web apps. We are now
developing a position on the appropriate use of client-side validation
in Web apps. More from the standpoint of saving an unnecessary server
trip on basic validations...we won't rely on client-side.
Struts provides for client-side validation using the same framework
(xml file) you set up for the server-side validation rules.
- Have you used the client side validation successfully? Any setup or
implementation issues?
- How verbose is the code?
- Is it cross-browser compatible?
- Is the code accurate and free of bugs?
- Which of the standard client-side validations do you use?
Any insight you have would be appreciated.
to provide insight.
We have been using the Struts validator (server-side) successfully for
both page level and field level errors in J2EE web apps. We are now
developing a position on the appropriate use of client-side validation
in Web apps. More from the standpoint of saving an unnecessary server
trip on basic validations...we won't rely on client-side.
Struts provides for client-side validation using the same framework
(xml file) you set up for the server-side validation rules.
- Have you used the client side validation successfully? Any setup or
implementation issues?
- How verbose is the code?
- Is it cross-browser compatible?
- Is the code accurate and free of bugs?
- Which of the standard client-side validations do you use?
Any insight you have would be appreciated.