> I considered this, but the documentation for SessionState makes it > sound like it is a very heavy handed solution, Whereas, the > documentation for Flash Persistence makes it sound like the right fit.
Both @Persist (flash, and session) and @SessionState (via ApplicationStateManager) use the HttpSession to store the value. The difference is that with @Persist it's tied to the particular page via naming of the attribute key and @SessionState does not, making it available across pages. Flash persistence simple deletes the item out of the session after it has been read once. Josh On Wed, May 19, 2010 at 1:04 PM, Pete Poulos <pete.pou...@gmail.com> wrote: > Hi Thiago, > > Thanks for your quick reply. > > >> Instead of using @Persist, why not creating a class to hold the message and >> use it as @SessionState? Just remember to clear the field with the message >> after it is requested. > > I considered this, but the documentation for SessionState makes it > sound like it is a very heavy handed solution, Whereas, the > documentation for Flash Persistence makes it sound like the right fit. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- -- http://www.bodylabgym.com - a private, by appointment only, one-on-one health and fitness facility. -- http://www.ectransition.com - Quality Electronic Cigarettes at a reasonable price! -- TheDailyTube.com. Sign up and get the best new videos on the internet delivered fresh to your inbox. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
