Hi,
I'm still battling this issue. I have a working quickstart that
demonstrates the issue we have.
Should I open a ticket?
Kind regards
Thijs
On 12-12-2012 15:07, Thijs wrote:
No it doesn't hit the browser cache.
It's actually recreating a new Page. We've put breakpoints in Wicket
to
Yes, please.
On Wed, Dec 19, 2012 at 2:16 PM, Thijs vonk.th...@gmail.com wrote:
Hi,
I'm still battling this issue. I have a working quickstart that
demonstrates the issue we have.
Should I open a ticket?
Kind regards
Thijs
On 12-12-2012 15:07, Thijs wrote:
No it doesn't hit the
Done: https://issues.apache.org/jira/browse/WICKET-4932
Thanks in advance for looking
On 19-12-2012 13:47, Martin Grigorov wrote:
Yes, please.
On Wed, Dec 19, 2012 at 2:16 PM, Thijs vonk.th...@gmail.com wrote:
Hi,
I'm still battling this issue. I have a working quickstart that
demonstrates
It seems that the browser tries to load the page from its cache.
I think you need to set proper cache headers to always ask the server
instead of using the local data.
On Tue, Dec 11, 2012 at 6:59 PM, Rob Sonke r...@tigrou.nl wrote:
Yes I know but by using the back button it seems to be
No it doesn't hit the browser cache.
It's actually recreating a new Page. We've put breakpoints in Wicket to
establish that.
In PageProvider is trying to create a new Instance see the stacktrace.
The following stacktrace is taken when we use the 'backspace' or 'back
button' in the browser
On Mon, Dec 10, 2012 at 9:04 AM, Rob Sonke r...@tigrou.nl wrote:
Last week we fixed an issue with Wicket 6 where mounted pages were being
reconstructed after the session expired. That was due to this (new) setting
which we set to false now:
Yes I know but by using the back button it seems to be ignored. Like it
tries to serve the same page no matter we have a session or not.
On Tue, Dec 11, 2012 at 9:59 AM, Martin Grigorov mgrigo...@apache.orgwrote:
On Mon, Dec 10, 2012 at 9:04 AM, Rob Sonke r...@tigrou.nl wrote:
Last week we
Last week we fixed an issue with Wicket 6 where mounted pages were being
reconstructed after the session expired. That was due to this (new) setting
which we set to false now:
getPageSettings().setRecreateMountedPagesAfterExpiry(false);
This worked perfectly for clicking on (ajax) links but,
