User tracking (ie sessions) is all managed by the servlet container - you do not need to worry about this.
When you access the session, you will be accessing the session for a particular user, ie whoever is making the request. To store a user's particulars in the session you can use the Tapestry service ApplicationStateManager: @Inject private ApplicationStateManager stateManager; So a user enters in login name, password. You do validation and return a User object: User user = userDao.get(loginName); stateManager.set(User.class, user); The object user is now a SessionStateObject (SSO) and can be accessed from any page or component where you @Inject the ApplicationStateManager: User user = stateManager.get(User.class); Cheers R. On Fri, 2011-02-18 at 04:49 -0800, robnangle wrote: > Yes that's what I mean. I have the login logout working, as in I have the sql > code checking if it is a valid user. What I am confused about is how to > store the user's who are logged in and know when they logout. > > Cheers --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
