You can increase the session lifespan if you want, but it's always better to just code to the worst case scenario... so whatever happens when the session expires should be well-defined. Is it possible that the session-scoped ASO is being created dynamically once the session expires, but it's not getting initialized like it would when the user logs in? If so, try to use the InjectStateFlag to check if the ASO exists without dynamically creating it.
On 4/4/06, Izak Wessels <[EMAIL PROTECTED]> wrote: > > Anybody able to shed some light on this issue? > > On 4/3/06, Izak Wessels <[EMAIL PROTECTED]> wrote: > > Ok, the reason I am asking is because when the user logs on to my > > application, it creates a session for that user. the user has an > > associated id that is being accessed on most of the pages throughout > > the application. however, after a period of time, when i try to load > > one of the pages, where the user id is being used, again it comes back > > and says that user id is equal to null. > > > > would this be a case where i simply need to increase the session > > lifespan in web.xml? > > > > On 4/2/06, D&J Gredler <[EMAIL PROTECTED]> wrote: > > > AFAIK, its lifespan will be the same as the session's... so until you > > > invalidate the session or the session expires (as defined in web.xml). > > > > > > On 4/2/06, Izak Wessels <[EMAIL PROTECTED]> wrote: > > > > > > > > Hello all, > > > > > > > > I was wondering if somebody could inform me as to what the lifespan > of > > > > an Session - Application State Object is? > > > > > > > > Regards, > > > > > > > > -- Izak > > > > > > > > > --------------------------------------------------------------------- > > > > 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] > >
