Hi all,

we are using wicket 1.2.5 and  we have "page expired" problems in our 
application with 3 frames.
In the main frame we are displaying some results in an 
AjaxFallbackDefaultDataTable. By using the paging mechanism and 
afterwards clicking on a link in the top frame the error occurs.

Back to the roots i played around with the wicket-examples for frames 
and the problem is there as well after clicking around for a while.

How can i avoid this problem? Are there any "best practices" beside the 
wicket examples?

Regards,

Michel

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to