In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] says... > The options of a <SELECT> control are only used to help the user choose a > value; its only purpose is to give the <SELECT> control a value and isn't > itself a value of the form. Think of it this way: the form doesn't lose > any data by changing your <SELECT> into an <INPUT type=text>. > Confused? Think of it another way: The <OPTION> values don't get submitted, > only the value of the <SELECT>.
Ahh, that make sense. Thanks. A followup question if I can... The ActionMapping that my XXXAction returns forwards to the same XXX.jsp that was used as the original input for XXXAction. I have noticed that, in XXXAction, if I change the value of one of the ActionForm variables, the JSP will plug the new value into the <INPUT> when it serves it back to the user. That's sort of neat, but it makes me wonder what will happen if an ActionMapping from another unrelated Action forwards to XXX.jsp. The other action may well have setup the customers variable in the context, but it is unlikely that it will have the same form as XXXAction. What happens in this case? Thanks again. -- Craig Edwards Sydney, Australia --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
