Oh okay, I see where the confusion is. You don't actually loose any information by reloading the bean everytime. It makes sense if you walk through the process:
-Page is requested for the first time. Bean is loaded, and form fields are populated. -User changes some fields, and hit's submit. A fresh bean is loaded, but all the fields that the user chaged are then set on the fresh copy. -Voila, the fresh copy is in the same state as it would have been if you'd kept it around. Basically, all the information that you'd need to store is already beeing stored for you in the user's browser. On 11/3/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > I dont get it. You are using the persistent pojo as a form bean? Isnt this > the whole point of the discussion? So why would you want to reload the form > bean every request? you would lose the submitted info if you did? > > -Igor ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
