RE: [OT] CheckBox and Boolean[] Array - Incorrect Values Submitted When CheckBox is unchecked

[Andrew Hill]

rofl

-Original Message-
From: Dave Derry [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 04, 2002 20:49
To: Struts Users Mailing List
Subject: [OT] CheckBox and Boolean[] Array - Incorrect Values Submitted
When CheckBox is unchecked


He's doing it as a service for those who are filtering you Mark!;-))


- Original Message -
From: "Galbreath, Mark" <[EMAIL PROTECTED]>


> Hey man!  RU refactoring my messages?  ;-)
>
> -Original Message-
> From: Andrew Hill [mailto:[EMAIL PROTECTED]]
>
>
> For multiple, you also must set values back to false in reset() (The
> question here of course is which checkbox refers to which element. You may
> need to refactor such that your checkboxes return non boolean values so
you
> can tell which is which at the server end).
> The reason for this is that the html spec in all its gory... uh I mean
> glory... has in its infinite wisdom defined that a checkbox (& radio
button
> I think) that has not been ticked will not submit any value to the server.
> Afaik same is true for SELECT btw (multiple selections where nothing
> selected)
>



--
To unsubscribe, e-mail:

For additional commands, e-mail:



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: [OT] CheckBox and Boolean[] Array - Incorrect Values Submitted When CheckBox is unchecked

[Galbreath, Mark]

Thanks a lot, Jerry.

;-)

-Original Message-
From: Dave Derry [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 04, 2002 8:49 AM
To: Struts Users Mailing List
Subject: [OT] CheckBox and Boolean[] Array - Incorrect Values Submitted
When CheckBox is unchecked


He's doing it as a service for those who are filtering you Mark!;-))


- Original Message -
From: "Galbreath, Mark" <[EMAIL PROTECTED]>


> Hey man!  RU refactoring my messages?  ;-)
>
> -Original Message-
> From: Andrew Hill [mailto:[EMAIL PROTECTED]]
>
>
> For multiple, you also must set values back to false in reset() (The
> question here of course is which checkbox refers to which element. You may
> need to refactor such that your checkboxes return non boolean values so
you
> can tell which is which at the server end).
> The reason for this is that the html spec in all its gory... uh I mean
> glory... has in its infinite wisdom defined that a checkbox (& radio
button
> I think) that has not been ticked will not submit any value to the server.
> Afaik same is true for SELECT btw (multiple selections where nothing
> selected)
>



--
To unsubscribe, e-mail:

For additional commands, e-mail:


--
To unsubscribe, e-mail:   
For additional commands, e-mail: