We have a central WebPage, which is not supposed to be versioned.
So, we call setVersioned(false) in all constructors for that WebPage, and
Wicket, indeed, has only one version for that page, version number 1.
However, it looks like somehow there is a logic inside the framework, which
is not aware of the fact that the page is not versioned.
Namely, when we click on some links
(/servletMap?wicket:interface=wicket-0:1:loginLink::ILinkListener) on other
pages, or even simply closing modal dialog boxes on that central WebPage, we
get "Page expired".
Further analysis shows that when the code like that
page.setResponsePage(new FNMyPhotosWebPage());
is executed inside our code (processing link click for example), Wicket
somehow creates a reference to the version number 2 of that WebPage, and -
obviously - it causes "Page expired", as the version number 2 has never been
created in the first place.
We use Wicket version 1.2.4 .
Are we missing something? Or is it a bug? What can we do to troubleshoot
this problem? Please, give us a hint...
Thanks in advance,
Bob.
--
View this message in context:
http://www.nabble.com/Version%3E1-and-%22Page-expired%22-despite-setVersioned%28false%29-call-in-a-WebPage-constructor-tf3236733.html#a8995918
Sent from the Wicket - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
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
