I think you have to provide more information, because in general
evicting the page from in -memory store just mean it must be reloaded
from the PageStor/DataStore! If this fails, then your application most
likeley has serialization issues.
So what is the "crash" you encounter? Why is it not feasable to have at
least 2 pages stored if it solves your problem? and so on...
Am 21.07.2015 10:33, schrieb tomask79:
Really no one? Nobody solves problem of having refreshing timer in pages and
using PageNumberEvictionStrategy(1) because this obviously doesn't work when
you're redirecting to another page again with timer....You can end up in
situation that previous page is dropped, but timer sent ajax already, wicket
then recreates page again but without pageparams => crash...
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
