Hi, This is what I like about Wiket.
Even if I start with a stateless page! So I update a component, and Wicket takes care of it via server side state - job done. The page is then no longer stateless which is fair. But: When the user stays on this page and the session expires, then even simple Links on the page like a sign-out link that do NOT require state cause PageExpiredException. In this case the beautiful advantages of using Wicket are gone. Working around these issues can be very expensive because one has to examine every single page in the special session expiry scenario. The workaround code becomes very ugly. Are there any plans to fix this or is this a feature? Bernard On Fri, 8 Feb 2013 09:09:34 +0100, you wrote: >Hi, > >It is OK. >But you can also just update some field/model in the current page instance. > > >On Fri, Feb 8, 2013 at 7:00 AM, snair ><sreelatha.n...@transport.wa.gov.au>wrote: > >> Is it ok to call the same page using setResponsePage(), only calling a >> different constructor, since the page now needs to display additional >> information, which I will be passing into this new constructor? For >> example, from PageA, can I say setResponsePage(new PageA(String a)) when a >> submit button button is clicked. >> >> >> >> -- >> View this message in context: >> http://apache-wicket.1842946.n4.nabble.com/call-the-same-page-using-setResponsePage-tp4656192.html >> Sent from the Users forum mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> 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
