Hunter,
In your Action, if you set the value of associatedSalesperson =
getEncodeAssociatedSalespersonID(), then it should fix your problem. Once
the form gets submitted, you can then do some processing on the value of
associatedSalesperson before writing the value to your database. Either way,
associatedSalesperson is going to get the one of the values
("Jobs-8","Bob-7","Bob-27", or "Bob-32").Regards, Richard -----Original Message----- From: Hunter Hillegas [mailto:[EMAIL PROTECTED] Sent: Monday, August 18, 2003 2:21 PM To: Struts List Subject: Re: html:select Not 'Selecting' My Item This may be the crux of my problem. For some reason (not immediately sure why), I thought I could have the contents of 'value' evaluated (i.e. value='${myOtherProperty}'). You're saying that this is not the case? If that's true, how would I get the effect I require? Thanks very much for your help. Hunter > From: Wendy Smoak <[EMAIL PROTECTED]> > Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > Date: Mon, 18 Aug 2003 14:09:22 -0700 > To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]> > Subject: RE: html:select Not 'Selecting' My Item > > No, 'value' is where you would put the literal value of the option you > want to be selected. > > Take a look here: > http://jakarta.apache.org/struts/userGuide/struts-html.html#select > > For 'value' it says: "The value to compare with for marking an option > selected." > > Nothing about using whatever you put in value as the name of a > different form property. Where did you get that idea? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
