On 6/6/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote:
Hi Matthias!
> You mean client/server attribute?
> this is a no-no (search the mail archive)
I know about the limitations of its current approach, but I meant to
extend this library to honor a global flag too.
I remember Craig isnt against such a flag - I think its just a matter of
no time.
> To me Cagatay's solution is better.
So extend Craigs validation solution with such an global configuration
flag and you are done.
Not Craig's, IIRC; I thought David Geary did at least the initial work.
Frankly, I find the Shale Validator code rather poor from a variety
of angles. First, using one Validator class and one JSP tag for all
of the different types is painful for users and tools support. Second,
supporting "client-only" validation (client=true, server=false) is a bad
idea that should not be copied; client-side validation should always
be *in addition* to server-side validation. Third, you should not have
to attach a validator tag to get "required" client-side validation
working; that should only require setting required="true" on the
component (and setting the global flag to activate client-side validation).
Finally, using a date "validator" for verifying formats of dates is
wrong; format masks should get checked by Converters, not Validators.
So, I'm -1 for extending any of that codebase. MyFaces can do much
better.
-- Adam
