On 11/19/05, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
I don't think this is what setPersistent() is intended for, and more than that, using it for re-displaying old values doesn't work, at least with wicket-1.1 (I tried it).
if you set defaultFormProcessing to false, calling setPersistent() on the form will not do the trick.
They are currently two solutions emerging, that are under discussion in this list, please search the archives with the "Preserve form state" subject : First e-mail from Matej, and last post from me with an example on how to implement this in core (not exhaustively tests, though).
Please give it a check and some feedback.
Laurent> BTW: when I did the 'custom form processing' I also wanted to call
> Form.persistFormComponentData() but this is private. Should this be called
> when Button.defaultFormProcessing = false.
>
use formComponent.setPersistent(true) instead. Wicket will do the rest.
I don't think this is what setPersistent() is intended for, and more than that, using it for re-displaying old values doesn't work, at least with wicket-1.1 (I tried it).
if you set defaultFormProcessing to false, calling setPersistent() on the form will not do the trick.
They are currently two solutions emerging, that are under discussion in this list, please search the archives with the "Preserve form state" subject : First e-mail from Matej, and last post from me with an example on how to implement this in core (not exhaustively tests, though).
Please give it a check and some feedback.
