Just to prevent nullpointers, in your onActivate() you should have if (object == null) object = new Object(). Obviously that could lead to unexpected results to the user - based on object state you could present a a message to the user etc. but there are quite a few different cases that you need to handle. Or you can detach the "page timeout" from session timeout and use some type of conversations, e.g. http://docs.codehaus.org/display/TRAILS/Conversations+in+Trails.
Kalle On Thu, Sep 17, 2009 at 2:08 PM, Michael Gentry <mgen...@masslight.net> wrote: > Is there a way in T5.1 to have graceful session timeout handling on > form submission or links? > > For example, I have a form with a bunch of inputs and I wait to click > the button until my 2-minute session times out (I'm > developing/debugging, so a short session expiration). When I submit > the form, I get NPEs because the objects I required (and used @Persist > on) are no longer there. I'd like a way to gracefully handle that and > present a message or something. I've been searching the list, the > documentation, the wiki, and the JumpStart, but still haven't found > the right magic. > > Thanks, > > mrg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
