gt; Sent: Tuesday, June 5, 2007 7:38:27 AM
> Subject: Re: [Wicket-user] Getting sent to PageExpiredErrorPage when page is
> not expired
>
>
>
> when i was running into this, it turned out that we were losing the session
> cookie. try checking the jsessionid cookie before an
wicket-user@lists.sourceforge.net
Sent: Tuesday, June 5, 2007 7:38:27 AM
Subject: Re: [Wicket-user] Getting sent to PageExpiredErrorPage when page is
not expired
when i was running into this, it turned out that we were losing the session
cookie. try checking the jsessionid cookie before and after and see if
when i was running into this, it turned out that we were losing the session
cookie. try checking the jsessionid cookie before and after and see if it
changes.
jayTSM wrote:
>
> This behavior seems to be happening on non-ajax requests. The component
> being submitted is a basic subclass of the
This behavior seems to be happening on non-ajax requests. The component being
submitted is a basic subclass of the wicket Form class. The pre-processing
before the submission involves setting the response page to the current
page, via the setResponsePage method on the wicket Component class. In
ad
We've had a couple of instances where this happened for Ajax requests.
Should be fixed now though.
Can you tell us more about which version you are using and what kind
of pages/ functionality you see this with?
Thanks,
Eelco
On 6/4/07, jayTSM <[EMAIL PROTECTED]> wrote:
>
> Sporadically, I'm see
Sporadically, I'm seeing form submissions rerouted by wicket internally to
the pageExpiredErrorPage, when it seems the requested page is not expired.
Does anyone have any ideas why this might be happening? These
page-expiration error cases seem to occur when the form's response page is
set to the
