I would use the Request for such a List and wouldn't even bother putting it in the ActionForm (unless of course the list is something the user is actually editing, then yes, you'd add that List as an ActionForm property). I try to keep my ActionForm with 'only' properties that the user can edit - nothing more. So for example if you were displaying a list of favorite cars for the user to pick from I would just put that list in the Request and the "selectedCar" would be the property you would concern youself with in the ActionForm. (If you are worried about performance, I'd put the performance concerns on the backend.. let the back end take care of any list caching.)
On 12/26/05, Paul Benedict <[EMAIL PROTECTED]> wrote: > > I am going to ask a related question... so take your best shot :-) > > I have an edit form in which I have to load a list from the database. The > list is actually based > on locale. What's the best solution here? I am using real action forms - > not that dynafluff stuff > ;) Is it to simply make my form session scope and attach the list to my > form? > > THANKS! > Paul > > > > > __________________________________ > Yahoo! for Good - Make a difference this year. > http://brand.yahoo.com/cybergivingweek2005/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Rick
