I think you're right - I would need to use the Session or the Database on each Ajax invocation to add these values.
But it also seems that if I store the new, dynamic, page specific values into a TextField (as opposed to a div) - they survive a page refresh. I'm not sure if that is robust or formally a standard across all browsers - so I will do a bit more research but that seems to be the behavior I'm after. Thanks, -Luther 2009/6/11 Dorothée Giernoth <[email protected]> > Hmm, is that possible ... you can't like store session-data in the browser, > do you? You can only store session-details in the database on the fly with > ajax while the user still fills out the form to allow the user to re-create > the session on next login or something like this if he accidently hits > reload (but even then I am not sure if that works ... maybe if you write the > not yet submitted but in the form included information back into the fields > when the site is rendered) ... > > Does that make sense ... or I am not understanding the question ;) > > - dg > > > -----Ursprüngliche Nachricht----- > Von: Luther Baker [mailto:[email protected]] > Gesendet: Donnerstag, 11. Juni 2009 13:27 > An: [email protected] > Betreff: refresh page > > If I add a few values to a page <div ala an Ajax button - and the user hits > refresh on the page, the new values I've added go away. > > The user is completing a form - but hasn't formally submitted the form yet > - > so there is nothing stored in the database yet. The browser naturally > re-renders the <textarea and <input values to the screen - but wipes out > content to any <divs I might have dynamically added data to. > > What would be the wicket way to allow these "dynamic divs" to survive a > page > refresh? Maybe on the a 'wicket-example'? > > Thanks, > > -Luther > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
