In my experience the most often case is when I have a non-serializable field in a page with Ajax components.
On the first Ajax interaction the serialization fails (SerializableChecker logs its detailed exception) and on the next Ajax request Wicket cannot find a page with the latest version and complains with PageExpiredException. So "page expiration" is not exactly "session expiration". Session expiration is just one of the cases in which your page(s) is(are) lost. El mié, 04-03-2009 a las 14:39 +0100, Dave Schoorl escribió: > This normally happens when your HttpSession expires. I'm not sure what > could be the reason in your case. > > > Edwin Ansicodd wrote: > > I see in the Page maps documentation: > > > > http://cwiki.apache.org/WICKET/page-maps.html > > > > that Page Exoured will be shown if the id and version for a page doesn't > > exist. But I can't see how the id and version of the page would not exist > > anymore. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
