Did you already look at StatelessForm?
Regards,
Erik.
Op 26-07-10 23:14, Erik Brakkee wrote:
Hi,
I am experimenting a bit with page expiry. One solution that works is to
remove the page from the pagemap in the submit of a form. However, removing
the page from the pagemap in the
I have added a configuration in the application to redirect the user to a
particular page. I guess page expires due to a timeout?
In the base application's init()
IApplicationSettings settings = getApplicationSettings();
settings.setPageExpiredErrorPage(LoginPage.class);
If that helps in
Hi
Saw a related link to force page expiry probably might throw some light
http://apache-wicket.1842946.n4.nabble.com/Force-page-expiration-td1844190.html#a1844190
cheers
On Tue, Jul 27, 2010 at 3:23 PM, Nivedan Nadaraj shravann...@gmail.comwrote:
I have added a configuration in the
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 isList of items -
Thinking about it some more.
Perhaps the best solution is to simply use a detachable model for the entity
in the view page and then send the user to an error page when the entry is
no longer there. I could of course also use a detachable model for the
entity on the edit page because in this page
Made some progress. Now I am removing the page from the page map in the
onDetach() and now expiry is really successful. Even so successful that the
form submit fails because the page has expired. This is of course logical
because the page object is still needed to process the form submit and now I