Good time Burton,
Thank you for your code but I think adding a new parameter maybe is not
a real necessary in this case. If we add it then it crowds check box tag
out more, confuses users with more options, needs support for a long
time and needs documentation. Maybe these are not necessary in
As a followup to my last email, it appears the Struts default design
pattern for checkboxes (submitting false values with hidden value) is the
cause. An easy fix for this would be to allow the developer to override
this design pattern by a s:checkbox parameter (e.g. requiredValue). The
default wo
Got it. I'll use that for now. Don't you think that is a bit of a hack?
Do you think this be fixed or reported as a "bug"?
On Sun, Oct 1, 2017 at 7:54 AM, Yasser Zamani
wrote:
> Hello Burton,
>
> Thank you; I examined your example and found out this behavior is
> because of something in Struts
Hello Burton,
Thank you; I examined your example and found out this behavior is
because of something in Struts named "automatic checkbox detection",
CheckboxInterceptor.
When your `choices` count is bigger than 1, you'll see your desired
behavior because CheckboxInterceptor does nothing with f
4 matches
Mail list logo
