Ah, then you need conversation scope as Dragan has suggested.... I was just checking ;) On 7 Nov 2013 11:19, "Dmitriy Vsekhvalnov" <dvsekhval...@gmail.com> wrote:
> Well, if you don't save your object(s) in memory you should save in some > other place, right? > > So, what are you doing if you have to edit object with several > pages/screens before finally committing it? > > > On Thu, Nov 7, 2013 at 2:03 AM, Thiago H de Paula Figueiredo < > thiag...@gmail.com> wrote: > > > On Wed, 06 Nov 2013 18:37:24 -0200, Lance Java < > lance.j...@googlemail.com> > > wrote: > > > > Any time someone wants to use the session, I always ask why. I avoid > >> session usage wherever possible. If there's no real need for it, I > >> suggest you keep your app stateless and use the page activation context > / > >> event > >> context to pass parameters. > >> > > > > Agreed 100%. Besides the lower memory usage, it also avoids some > problems. > > > > -- > > Thiago H. de Paula Figueiredo > > Tapestry, Java and Hibernate consultant and developer > > http://machina.com.br > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > >
