Hmm... interesting. Thanks for pointing that out. But I don't think
that's it.
Check and see what is going back to the server in terms of form
values when you submit the form. The fix, IIRC, is to put a dummy
hidden field in the form so that WO processes takeValues.
The strange thing is that in a dummy test app I've just made, it
too only has checkboxes in the form but even if I make no changes
to the form the child component still has its setter methods called
during the takeValuesFromRequest phase. But in my app-proper it's
being skipped.
I've tried putting in the hidden field, but that didn't help - so
something else is skewed :-/
I'll try turning on DebugGroupComponents, DebugGroupRequestHandling...
Any other suggestions?
What do you see for form values? Forget to call super.takeValues
someplace?
Chuck
On Jul 30, 2007, at 6:05 PM, Lachlan Deck wrote:
okay this is a little weird, from my understanding of WO...
I have a page with a form and in the form is a repetition of a
sub-component which has a checkbox and associated logic with that
checkbox.
So something like this:
<page>
<webobject name="Form">
<webobject name="ListItem"/> <!-- has a checkbox -->
</webobject>
</page>
However, when ticking or unticking the checkbox in any of the
ListItem components (where I've bound checked = isSelected) I'm
finding that setIsSelected is not being fired in the subcomponent.
