On 5/12/05, Pedro Salgado <[EMAIL PROTECTED]> wrote: > > Well, your option 1) matched the #2 > and > 2) matched the #4 > > :) > > Pedro Salgado
It might be helpfult to clarify whether by output we mean output that is being used within the <html:form> tags, or any arbitrary dynamic output. The intended use of the ActionForm is to represent the values of the controls *within* a form. In Struts 1.1, the scope crept so as to include, for example, lists used to populate controls. The cannonical role of the ActionForm is to represent what the user might input into the form, or to default input on behalf of the user (e.g, to edit values previously input.) I don't know if the latter case, providing default input values, counts as "output" in this thread. Plunking into an ActionForm something like a result list from a search query is an unintended use. The ActionForm was not designed as a Velocity context, but as a way of vetting input from forms. If people are putting result lists on ActionForms, that don't represent input values, then I can understand why multiple ActionForms might be an issue. But, personally, I don't see a compelling argument for putting arbitrary dynamic data on an ActionForm. Any POJO would work as well. I could see a case for a Velocity-type Context that might include an ActionForm as a member, but I would not recommend trying to subvert ActionForms as a Velocity-type Context. If people want a Velocity-type Context, then let's do that, and put the ActionForm inside the page Context. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
