On Mon, 21 Feb 2011 07:40:42 -0300, Richard Hill <r...@su3analytics.com>
wrote:
This just puts the retrieved user object into the session as an SSO.
This means it is accessible from all pages/components, unlike say
@Persist'd quantities which are scoped to individual pages/components.
You can stick whatever you like into the session, but for reasons of
overhead should really be limited to simple objects or primitive types.
Remember that, for @SessionState, it's not recommended to use types like
String or primitive types, as @SessionState is segregated by object type.
--
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
