Thanks for the reply Martijn.
I have done some poking around and I think this thread holds the key:
http://apache-wicket.1842946.n4.nabble.com/PageExpiredException-ajax-request-td1878866.html#a1878866
PageExpiredException - ajax request
It looks like our 'stateless' page gets rendered with
On Thu, Jul 1, 2010 at 2:30 AM, sbrookes2 seanbroo...@shaw.ca wrote:
It turns out that isn't the only source of these messages as it seems to be
related to using AJAX behaviors on stateless pages causing the pagemap to
either lose or remove references to certain pages so that when an AJAX
ver 1.3.6
I have been tracking this issue for a few months now in our app. Similar to
the following threads:
http://apache-wicket.1842946.n4.nabble.com/PageExpiredException-getting-this-when-the-session-hasn-t-timeout-td1894202.html#a1894216
PageExpiredException - getting this when the session
So far I traced this down to the fact that sometimes some wicket:interface
requests (in our case used in img src and in anchor 'href) do not include a
jsessionid - either as a ;jsessionid= URL param or a cookie - thus no
session can be found.
The container's impl of
We're interested in this as well, as our logs are full of these as well.
On Mon, Apr 12, 2010 at 10:32 AM, Nikita Tovstoles
nikita.tovsto...@gmail.com wrote:
So far I traced this down to the fact that sometimes some wicket:interface
requests (in our case used in img src and in anchor 'href) do
Here's a typical exception:
00:01:17,644 ERROR CLPWebRequestCycle:34 - Cannot find the rendered
page in session
[pagemap=null,componentPath=7:results:resultsInfo:criteriaContainer:inputPanel:categorySearchForm:submitLink:searchButton,versionNumber=0]
