The ActionForm (there is no ActionFormBean) is the basic form bean. You can use this or any subclass for Struts form beans. You use them to hold the values passed from the browser. These values can come from a <form>, from multiple <form>s through multiple pages, or even from parameters at the end of a URL (like "/webapp/path.do?fname=Bill&lname=Ding").
For ValidatorForm, DynaValidatorForm, and DynaValidatorActionForm, see http://marc.theaimsgroup.com/?l=struts-user&m=110375387629389&w=2 ValidatorActionForm is the non-dynaform version of DynaValidatorActionForm. What this means is, you can specify how it's validated through XML, and the Validator plugin will find the set of rules to apply to it based on which path it gets submitted to. LazyValidatorForm is a dyna form that doesn't need to have its fields specified in a config file. You can declare a bean to be a LazyValidatorForm and it'll create the necessary fields as values are passed to it. BeanValidatorForm is a new form bean which can be backed by a POJO. Through this class, you can use your own business object to back a form bean. I believe this will work better if you're using 1.2.5 or higher. Note that ActionFormBean is a configuration object, DynaActionFormClass is a DynaClass implementation; neither of these are ActionForm subclasses and should not be used as form beans. Hubert On Tue, 11 Jan 2005 15:52:17 -0700, Daniel Watrous <[EMAIL PROTECTED]> wrote: > 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
