I actually had this very problem last weekend; sorry I didn't read of yours until just now. The action mappings can be very confusing and I wish the documentation was clearer on the purpose of the various parameters and their effects on processing and page transitions. For the time being, it's pretty much trial-and-error.
Mark -----Original Message----- From: [EMAIL PROTECTED] Sent: Thursday, April 25, 2002 7:07 PM Arrrghh! As you may suspect, I was doing something foolish: I was looking at the wrong form. I didn't realize that, when matching up the properties of input fields set by <html> custom tags in an <html:form>, you need to match the fields against properties in the form associated with the action mapping which is the DESTINATION of the form, not in the form associated with the action mapping FROM WHICH CONTROL arrived at the form. Because of this, my fields didn't match my properties, and none would've been found by the Struts custom tags. This fact was somewhat concealed from me by a "false positive" from Struts: if in the <html:text> tag the 'value' attribute is set, *apparently* the tag doesn't check for a getter/setter pair that corresponds to the 'property' attribute. So, the page rendered fine until it got to the <html:radio> tag, which *apparently* DOES check for a getter/setter pair EVEN IF you supply a 'value' attribute. I spent too much time wondering my <html:radio> wasn't working and not enough time realizing that none of my tags were actually working. I'm sure most people would never have this problem, but to any who might, I hope this servers as a cautionary tale. Cheers, David -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
