Could you please elaborate what you mean by "session object has changed"?
Let's say I have some variables in my session. If these variables change, do I have to call session.dirty? ** Martin 2008/5/2 Matej Knopp <[EMAIL PROTECTED]>: > Hi, > > session.dirty() should be invoked when the session object has changed, > so that wicket changes the http session attribute to make cluster > replicate the session object (assuming you're running in clustered > environment). > > I think the only case when you need to call dirty() yourself is when > your application has only stateless pages and you have a statefull > session object that you need to replicate accros cluster. But IMHO > that's not very common usecase. > > -Matej > > > > On Fri, May 2, 2008 at 4:46 PM, Martin Makundi > <[EMAIL PROTECTED]> wrote: > > Hi! > > > > I have been coding without invoking session.dirty. Browsing framework > > code, I can see it is used. What does it accomplish and where should I > > have used it in my own code? > > > > ** > > Martin > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > Resizable and reorderable grid components. > http://www.inmethod.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
