On Jun 2, 2006, at 12:46 AM, Igor Vaynberg wrote:
i dont think this is a limitation at all
the button that submits the url is immediate right? that means the
form processing doesnt happen - and this is the intended behavior.
so the form components hang on to their raw input (the input the
browser sent) instead of refreshing it from the model - and this is
also intended otherwise if validation failed you would see whatever
value was in the model instead of whatever you just typed in when
the page refreshed. there is just no way for wicket to do this
automatically because it cannot see inside your brain.
OK, makes sense.
for your particular usecase i see a simple and elegant solution:
the form where you enter the url - that can be a separate form that
populates a model for another form that contains the rest of the
fields...that way i think everything will work smoothly.
Nope, that won't work. The submit button of the second form wouldn't
submit the first form, and I need the URL as well.
also, we have a builtin way to visit components - see
form.visitFormComponents which is nicer then the loop you have and
will also work its way recursively through the hierarchy so even
components burried in panels will be reached.
Yup, missed that, will rewrite it right away. This is what happens
when you deal with such a rich API...:-)
Thanks for your support,
--
Gianugo Rabellino
-------------------------------------------------------
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?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
