Yes, sorry, was thinking of @Persists there. SSO's are keyed by class: stateManager.get(User.class)
so for SSOs you can only have one of each class type. On Mon, 2011-02-21 at 08:33 -0300, Thiago H. de Paula Figueiredo wrote: > 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. > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
