Do you want that a onChange (onClick of a Check component) does a real submit?
It only does a "fake" submit and calls your onSelectionChanged method.
You shouldn't loose any input because everything is stored in the rawinput of the formcomponents
All other formcomponents are not stored to the models no. This only happens when you do Form.process()
johan
On 5/24/06, Ralf Ebert <
[EMAIL PROTECTED]> wrote:
Hi,
> yes. sometime back we had it working like what you want, but too many users
> complained that it was not what they wanted so we changed it.
unfortunatly, this pushes the values to the model and forces
validation. I think something else is not working with my form,
because when a field doesn't validate, this change and other client
value changes are lost as well. I'm using forms like I usually do
(except there is a panel with a separate compoundpropertymodel in
between). Was there some change in how values, which aren't pushed to
the model yet, are handled in wicket 1.2?
Ralf
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmdlnk&kid7521&bid$8729&dat1642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
