I have indeed seen how to set the default expiry page in the Application class and that might come in handy. Will have a look too at the StatelessForm.
Anyway, I have a working solution now with the pagemap trick. However, perhaps I need to do even more, because the flow is List of items -> view item page-> edit item page-> back -> back In that case, the first back leads to en Expired page. But, the second back button leads to the view item page showing incorrect contents of the modified item. This is probably because the edit item page has its own copy of the item (even though the edit page was constructed from the view page by passing it the item object). Possibly this happens because of serialization of individual pages. Therefore, the second time the back button is pressed I am viewing stale data. I could solve it perhaps by reloading the entity from the database in the view page's onBeforeRender() and even to check for its existence (item might have been deleted) and in the latter case forward to another page. Or am I going perhaps too far in trying to get consistent views of my application's model?
