Well, your option 1) matched the #2 and 2) matched the #4 :)
Pedro Salgado > #1 Prefer not to use action forms at all > #2 For input data only (usually collected from HTML form) > #3 For output only (to be used in JSP) > #4 Same form for input and output > #5 One form for input, another for output > #6 Other On 12/05/2005 14:04, "Ted Husted" <[EMAIL PROTECTED]> wrote: > My question would be: > > * Under this poll how does the Struts MailReader application use ActionForms? > > I would think the essential question is whether people use ActionForms to > > 1) Harvest or populate only the default values of form controls. > 2) Populate other page members, such as the items displayed on a > drop-down lists. > > In Struts 1.0, the design of the taglib implied (1). In Struts 1.1, we > extended the tags to make (2) more convenient. > > I tried (2) for a while, but went back to (1). > > I would say that (1) is the "cannonical" approach, and (2) is a > standard deviation. > > -Ted. > > On 5/11/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote: >> By the way, hopefully by input and output data we understand the same >> information. For example, this wiki page >> http://wiki.apache.org/struts/StrutsMultipleActionForms treats data >> from a page point of view: "Most pages have both input data (setup) >> and output data (request name/value pairs)." That means, that input >> (setup) data is used to build the page, and output data is sent from >> the page. I just noticed that ;) >> >> I treat data from action's point of view. Thus, input data is sent >> from the browser to the action, and output data generated by action >> and sent to the page. > > --------------------------------------------------------------------- > 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]
