Hi, I'm scratching my head a bit with my "user" object expiring in the session. I'm using the dispatcher method for setting up access control as in the wiki ( http://wiki.apache.org/tapestry/Tapestry5HowToCreateADispatcher2 ). Now everything is working great except that after around the 20 minute mark (of actively using the app) I'm presented with the login screen again. So what I think is happening is the session is expiring based off when the object was first created, and it isn't being updated.
I tried adding an applicationStateManager.set(...), thinking that might refresh the object, but that didn't work. As a side thing, shouldn't the session expiry timer start again every time the client accesses the session?, or do I need to actually call a method somewhere to update the session timer? Or does tapestry manage itself on-top of the session and I need to "refresh" every object I put in there? I am suprised because I have a few page @persist object in the session too, so I don't see how the session would expire... I'm currently using tapestry 5.1.4 on Jetty 6.1.15 Anyways, thanks for the help. Ryan -- View this message in context: http://www.nabble.com/T5.1-User-authentication%2C-session-expiring-even-though-sso-is-accessed-every-request-tp24475080p24475080.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
