Could it be that the onload ajax request somehow comes back from the browser before wicket creates the pagemap and binds it to the session?
Jonathan Locke wrote: > > This is a real bug in 1.3, it turns out, and I think it does not have > anything to do with cookies or application servers. > > I have verified in an application getting this exception that the session > id is constant for every request (modified wicket to print it out). > > The exception is begin thrown from line 141 of WebRequestCycleProcessor. > > Here's what I think is happening: > > An AJAX callback that occurs in the onload handler for the page executes > line 84: > > if (requestParameters.isOnlyProcessIfPathActive()) > > and finds it is true, then at line 90 > > IPageMap pageMap = > session.pageMapForName(requestParameters.getPageMapName(), > false); > > the session is retrieved, but it DOES NOT EXIST yet so the pagemap is null > then at line 97 > > processRequest = false; > > which causes the exception to be thrown. > > I do not understand this set/isOnlyProcessIfPathActive boolean's purpose. > > > -- View this message in context: http://www.nabble.com/PageExpiredException-Bug-tf3781043.html#a10693039 Sent from the Wicket - Dev mailing list archive at Nabble.com.
