Validator Design Questions

[Don Brown]

With the validator as a constant source of hangups, I'm working on 
becoming more familiar with how it works.  I have some questions, 
perhaps rather basic and obvious:

Why does Struts perform all its validation with o.a.s.v.CheckFields?  It 
seems it duplicates a most of commons-validator's, well, validators.  
Why not process the ValidationResults after validator.validate() to 
create the necessary ActionMessages and use commons-validator's existing 
validators?

This might more just validator specific, but why is there no facility to 
provide the validator an already existing instance of a Validator (or if 
there is, where is it)?  It seems the only options are to create a 
Validator with static methods or a no arg constructor.  I think it would 
be valuable to let Spring manage more complex validators that rely on 
business objects, and re-use those validators with Struts.  Or, perhaps 
you want a method on one of your existing business objects to be called 
for validation.

Thanks for the help,
Don
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]