Well, I know that. But the issue isn't getting the checkboxes to correctly set the bean properties, it's correctly setting the box state on the form page. If the boolean property is true, and I click on the link to edit the bean, I don't want to have to recheck the box (if the property was previously set to 'true') in order to preserve that property while changing other properties. I hope I'm being clear, do you know what I mean? It seems like a very undesirable struts issue.
~ Keith http://www.buffalo.edu/~kkamholz -----Original Message----- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 25, 2002 11:31 AM To: Struts Users Mailing List Subject: Re: <html:checkbox> On Thu, 25 Jul 2002, Kamholz, Keith (corp-staff) USX wrote: > Date: Thu, 25 Jul 2002 09:21:56 -0400 > From: "Kamholz, Keith (corp-staff) USX" <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > To: "Struts (E-mail)" <[EMAIL PROTECTED]> > Subject: <html:checkbox> > > Hey everyone, > I've just essentially finished my first struts application, and my boss > doesn't like the fact that the boolean properties associated with checkboxes > must be set to false when going to the form. He says that it's a pain in > the ass to recheck the boxes every time the bean is edited. I agree with > him. Is there any way to get around this issue? Possibly by modifying or > extending the checkbox class? I don't know if anyone has tried anything > like this, but any input would be greatly appreciated. > Thanks! > In the reset() method of your form bean, set the corresponding boolean properties to false. > ~ Keith > http://www.buffalo.edu/~kkamholz > Craig -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
