Please take a look at the patches / new versions of Form & FormComponent that I sent to the list early this week ( see the "Preserve form state" thread).

It is what I consider a pretty well formed hack that shows how I supposed form handling could work by default.

It could maybe be done differently, but the main spirit is there.

Matej, please take a look at it too.

--
Laurent

On 11/19/05, Christian Essl <[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).

I just wanted to use setPersistend() for setting a cookie which remembers
ie the username for the next login.

>
> if you set defaultFormProcessing to false, calling setPersistent() on the
> form will not do the trick.
>

I think so too. Maybe there is a workaround.

Christian







___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to