Hi Adam! > First, using one Validator class and one JSP tag for all > of the different types is painful for users and tools support. Yes.
> client-side validation should always be *in addition* to server-side > validation. Which should be the default for sure, I dont think that it soo bad if the user has additional decisions. > Third, you should not have > to attach a validator tag to get "required" client-side validation > working; As JSF currently is, it is the easiest way to handle this that way, else, you have to install a custom renderer - you know about the downsides of it. But for sure, it would be great to have this comfort. > Finally, using a date "validator" for verifying formats of dates is > wrong; format masks should get checked by Converters, not Validators. Its by the nature of a converter to fail if the mask didnt match, though, its arguable to say the validator will check the input at first, no? A converter can be much more complicated so that you cant easily check this by a client side validator, but describing only the syntax should be easy. The validator checks the syntax and the converter converts the value to an object, no? Notice, I was just an idea. Cagaty is nearly finished with his work, so including shale-validator is no longer in discussion. So lets see if his work fits our needs. Ciao, Mario
