Or, you can use a conversational scope - stored in session but as part of separate scope which can be set to expire earlier than the session itself. The library also supports multiple simultaneous conversations on different browser tabs. More at http://docs.codehaus.org/display/TRAILS/Conversations+in+Trails.
Kalle On Wed, Jul 22, 2009 at 4:19 PM, Thiago H. de Paula Figueiredo<thiag...@gmail.com> wrote: > Em Wed, 22 Jul 2009 05:51:23 -0300, Stephan Windmüller > <stephan.windmuel...@cs.tu-dortmund.de> escreveu: > >> It is really necessary to use a persistent store when all needed data is >> transmitted with each submit of the form? > > Tapestry does redirect-after-post by default, so some form of persistence is > needed. You can also use the activation context to pass this information > back to the page whithout usin @Persist or @SessionState. > > You can disable redirect-after-post (documentation at > http://tapestry.apache.org/tapestry5.1/guide/conf.html), but I don't > recommend this option. > > -- > Thiago H. de Paula Figueiredo > Independent Java consultant, developer, and instructor > http://www.arsmachina.com.br/thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
