Craig McClanahan wrote:
That makes more sense now.
I tend to put all my lookup data (for dropdown lists and such) into application scope (if its global) or session scope (if it's user specific), primarily as a performance enhancement ... I only have to look it up once, instead of once per request. As a side effect, you don't have to worry about the values going away, like you do if they are in request scope.
I try to do that also, but often times the lists you need to display are specific to the type of user logged in. In these cases, if I don't manually validate and then use the setUp() method to repopulate some Request scope stuff, I'll usually just stick the Lists in Session scope. If memory performance is a super major concern then I stick to the manual validate in the Action and repopulate the request as needed with the Lists it needs.
I notice this problem ( validation fails now lost select list on page ) comes up a lot on this mailing list. Probably time I updated a wiki somewhere of the various approaches you can take to accomodate this problem ( application scope, session scope, persistence layer caching, call validate manually, combination of the above, etc).
-- Rick
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
