--- Janice <[EMAIL PROTECTED]> wrote: > The only glitch is when validation fails, since my drop-downs come back > empty. So I'm thinking that I can get around this, but it'll mean extra > database calls and be a performance problem that way instead of just > hogging the session memory. I guess this is why I was told this stuff had > to be in the session... it all makes sense now.
That's where the three options come in. You can leave the drop-down values in the session, in the application scope, or in the request scope but use input="/mySetupAction". Whether the form itself is in session or request scope doesn't affect how the drop-downs get populated. hth, Hubert __________________________________ Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want. http://antispam.yahoo.com/tools --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
