Is it possible that it occurs when a user stays on a bookmarkable page
for a long time (the page having forms) and then clicks trying to
submit the form after the session has expired? Could I just nest a
hidden form field that I could use to determine the page? What would
be the right place to proc
bookmarkable urls do not generate a page expired error, the urls that
do generally look like this:
?wicket:interface=2:ff.sdfsdf.sdf:ILinkListener
where the only information you have about the page is "2".
you can write your own coding strategy that always appends the class
name of the last book
Specifically, if it is a Mounted Bookmarkable page, the page name
should be available in the url?
**
Martin
2009/1/16 Martin Makundi :
>> when you hit pageexpired exception you do not know which page caused it
>
> Is it possible that there could be some query parameters that could be
> used to de
> when you hit pageexpired exception you do not know which page caused it
Is it possible that there could be some query parameters that could be
used to deduce such information?
**
Martin
>
> On Fri, Jan 16, 2009 at 11:18 AM, Martin Makundi
> wrote:
>> Hi!
>>
>> I would like to ignore "page exp
when you hit pageexpired exception you do not know which page caused it
-igor
On Fri, Jan 16, 2009 at 11:18 AM, Martin Makundi
wrote:
> Hi!
>
> I would like to ignore "page expired" on certain pages. What I mean is
> that in general it is ok to follow the instruction:
>
> getApplicationSettings(
Hi!
I would like to ignore "page expired" on certain pages. What I mean is
that in general it is ok to follow the instruction:
getApplicationSettings().setPageExpiredErrorPage(LoginPage.class);
However, on certain pages where the session is not so important, I
would like to redirect back to the
