DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31365>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31365 Add initValue attribute to html:radio tags ------- Additional Comments From [EMAIL PROTECTED] 2004-09-28 19:59 ------- Joe wrote: > That contract says that "if value is supplied, use it, without > consulting the underlying bean"; so in the case where initValue > was implemented, when an invalid form was re-presented to the user, > the initValue would be consulted again regardless of what the user > had selected upon her prior submission. Not sure what you are getting at with the above, but surely the same would already apply to those tags (text, hidden, password) that do allow developers to set the initial values in the JSP. > Note that the same issue applies to checkbox, multibox, and select, none > of which have this kind of mechanism. But, not the same as the text, hidden, password and textarea elements, which all have an initialisation mechanism. I think the problem is that the user not only expects the radio tag to have a "initial value" attribute, but is also used to setting initial values through the "selected" attribute in the page itself as well. I think this is a case of mixed design: some initial values must be set in the control layer but some can also be set in the JSP form (view layer) which leads to confusion and frustration. We should either allow all html elements to be intialised in the view layer or only allow users to initialise values in the control layer in which case some framework to do this must be created. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
