Ok, good, then there is nothing obvious I'm missing. I think it would be
a good goal for Struts to use validator completely and not require its
own validators, and I will look into that. As for the loading of
validators, yes, I'll take that over to commons-dev.
Don
David Graham wrote:
--- Don Brown <[EMAIL PROTECTED]> wrote:
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.
The original design was for all validations to be loaded from an xml file
into a ValidatorResources object that Validator objects use against
beans/forms. I don't think adding resources at run time was considered.
The active validator team is really just Rob and me at this point so your
input is much appreciated. We should probably continue the discussion on
commons-dev though.
David
Thanks for the help,
Don
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
__________________________________
Do you Yahoo!?
Yahoo! Domains – Claim yours for only $14.70/year
http://smallbusiness.promotions.yahoo.com/offer
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
