On Thu, 06 Jan 2011 21:26:32 -0200, Bryan Lewis <jbryanle...@gmail.com>
wrote:
Interesting idea, I plan to try it... I've had occasional difficulties
getting the built-in persistence methods to work just right. If I use
flash, the message doesn't always survive the redirect, say if I return
null from onSuccess().
Flash-persisted fields are kept in the session until you read them. After
that, they're removed from the session. I've never had problems with them
not surviving a redirect.
But I'm curious about the original statement, "Generics are dangerous in
SessionState, in fact, SessionState is dangerous with anything but a
custom type." That's news to me, so I must be missing something.
Dangerous in the sense that it's easier to make a mistake and use the same
object type for different things, not anything about Tapestry itself. It's
way harder to have an application that ends up incorrectly using
@SessionState with an User class, for example, than it is for String.
Custom types are way more specific in usage and semantics, so it's
improbable you misuse them with @SessionState.
--
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
