> 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.
This is the strategy that I use. I have a UserMessageHolder object
stored as @SessionState and have a component that renders the
messages, much like t:error. This way in your code you simply write
userMessage.info("'%s' has been deleted."); and the next time the page
renders (that has the UserMessages component) the message is
displayed.
Josh
On Wed, May 19, 2010 at 12:53 PM, Thiago H. de Paula Figueiredo
<thiag...@gmail.com> wrote:
> On Wed, 19 May 2010 16:49:45 -0300, Pete Poulos <pete.pou...@gmail.com>
> wrote:
>
>> Hi,
>
> Hi!
>
> 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.
>
> --
> Thiago H. de Paula Figueiredo
> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and
> instructor
> Owner, Ars Machina Tecnologia da Informação Ltda.
> http://www.arsmachina.com.br
>
> ---------------------------------------------------------------------
> 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
