Hi All,

I've noticed something odd when using stateless forms (on a stateless pages, 
although this fact is likely incidental to the problem).

The problem is as follows:

When the form is submitted for the first time the form fields are made 
available (by wicket) as page parameters (as well as populating the model). If 
the page is subsequently reloaded (say if if there is an error on the form 
which is displayed back to the user) the original form fields are rendered on 
to the forms action query string (because they were in the map of page 
parameters). These then override the form fields when the form is subsequently 
submitted for the second and subsequent times. To get around this I am 
explicitly removing form fields from the page parameters map before reloading 
the page (or by overriding Page.getPageParameters() and removing them there) 
however I sense that I am doing something wrong and was wondering if anyone 
could point out what I'm doing wrong.

Many Thanks,

Joel Halbert

Reply via email to