That's how I do it. I store the user-id in the session inside one of my ASOs. Then, I have a threaded service called SecurityContext which actually will lazily load the actual user object during the request cycle if it's asked for by someone (like a security interceptor or something).
-----Original Message----- From: Andreas Bulling [mailto:[EMAIL PROTECTED] On Behalf Of Andreas Bulling Sent: Tuesday, April 18, 2006 5:50 AM To: Tapestry users Subject: Re: ICallback/Session problem Hi Ron, thanks for your answer! | I don't fully understand what your ICallback does and where in the work | flow it is activated - Well, actually as a first version I just took the one from the vlib example... When the user has been idle for some period of time the login page is shown again and he is able to re-login. After that the page he had visited before the session became invalid is shown. But this only works for pages where no database record has to be read in pageBeginRender() because the database id (which is normally passed for example as a parameter with a DirectLink) is unknown and an exception is thrown :( | My solution is to design pages that always work, thus, keep the minimum | necessary in the Visit (eg current logged in user-id) - the rest on the | client - And in your page classes (probably in a page superclass) you reload the user object from the id every time a page gets loaded? Sincerly, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
