property="list"/>
was indeed
the fix. Thank you Jim, you rock. What I don't understand is that I
thought I had tried that before as well and that it had screamed about
not finding the bean in any scope. I must have been giving the wrong
bean name - who cares?!
Thanks again,
Kevin
On J
I load my states in two arrays in a PlugIn -- the labels ("Alabama") and
the values ("AL"), and set them as application scope attributes.
Then I simply refer to those attributes in my combos, like this:
Because it's wrapped in an html:select with a property name that matches
one of my form bean
> -Original Message-
> From: Kevin McAbee [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 21, 2004 12:47 PM
> To: Struts Users Mailing List
> Subject: App scoped bean to be used with html:optionsCollection in JSP
>
As for thorough flamings... I like my meat medium rare :)
>
> // m
3 matches
Mail list logo