Good point, Rick. Isn't this the sort of thing that JSF allows?
Not sure haven't looked at JSF yet:) Plan to at some point. Craig?
Of course, you can bind a validation to an action mapping using the ValidatorActionForm -- however this still forces your business objects to extend this form and it doesn't solve the populate problem.
Well, I'm actually not talking about binding the validation to a "form" or any bean but binding it to a mapping. The framework then will look at the basic request parameters and validate them based on some configuration for the mapping and of course return back to the user any errors. It never gets to the population of the bean (POJO/VO whatever) until after validation succeeds. Of course you could still get an ugly conversion error there if you don't validate properly but that's the case with any system. At least with the above approach you aren't tied to having to rely on an ActionForm simply for validation purposes.
As far as the problem of migrating deeply nested VOs to Action Forms -- we have the same issues on the app that I am working on -- I feel your pain ;)
Yea, annoying - especially if you have to validate stuff that is nested:)
-- Rick
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
