It would seem that every form in my web application requires a form class (JavaBean). I think I understand that a Form is a loose term, not necessarily referring to one <form></form> tag set on a given page, but rather a form may span many pages and requests. Is this correct so far?
I think that I also understand the mechanism DynaActionForm, which builds a type of "Bean" from an XML definition of the form, rather than hardcoding an ActionForm subclass for the form. These two beans also provide a validate method (one inherited) which I can override (optionally) to perform validation. My question relates to several other classes that all seem to do similar things, but I'm not finding clarification about how to use them in the Javadocs, or User/Developer documentation. Most of them relate to validation. Of the following list, when is the most appropriate time to use each one, and what are their differences? ActionFormBean DynaActionFormClass BeanValidatorForm DynaValidatorActionForm DynaValidatorForm LazyValidatorForm ValidatorActionForm ValidatorForm I will continue with the Javadocs. Please send links to documentation that may clarify the use of each of these classes. Thanks in advance... Daniel
