If you have 15 *different* lists then, yes, you will need to store them all. But if 2 or more lists share the same options then you will only need one collection. On the example page, there are two lists of books, but they both get their options from the same request scope collection.
Also, you might not need to place your collections in the request each time. Depending on the list, you might be able to use the session or application scopes. For example, a list that all users share and does not change could be placed in the application scope at application startup. Steve > -----Original Message----- > From: Kommana, Sridhar [mailto:[EMAIL PROTECTED] > Sent: May 29, 2003 1:53 PM > To: Struts Users Mailing List; [EMAIL PROTECTED] > Subject: RE: html:select tag > > > your link explains very detail. > if i have 15 drop downs on a page means i need to give 15 > different request.setAttributes > PrepareOptionsAction has so many request.setAttribute things. > is any better way doing this with html:options. > > Sri > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
