This behavior seems to be happening on non-ajax requests. The component being submitted is a basic subclass of the wicket Form class. The pre-processing before the submission involves setting the response page to the current page, via the setResponsePage method on the wicket Component class. In addition a couple of objects are saved using hibernate before submission.
I am currently using the wicket 1.2.5 jar. Eelco Hillenius wrote: > > We've had a couple of instances where this happened for Ajax requests. > Should be fixed now though. > > Can you tell us more about which version you are using and what kind > of pages/ functionality you see this with? > > -- View this message in context: http://www.nabble.com/Getting-sent-to-PageExpiredErrorPage-when-page-is-not-expired-tf3867462.html#a10958877 Sent from the Wicket - User mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
