Hi,
Some time ago, we faced a similar issue. A custom component accessed
pages after they were unlocked, causing stale locks. Back then I filed
an issue (WICKET-6558), but haven't had time to implement the fix.
Locking pages after commitRequest should be blocked.
Best regards,
Emond
On Tue, Aug
Hi,
PageAccessSynchronizer#detach() unlocks all pages.
Is your request logger running after that?
Have fun
Sven
On 13.08.19 07:46, Martin Grigorov wrote:
Hi,
If the page is not unlocked then it is a bug.
But it is strange that no one faced it before. This code is in use since
Wicket 1.5.0.
Hi,
If the page is not unlocked then it is a bug.
But it is strange that no one faced it before. This code is in use since
Wicket 1.5.0.
On Tue, Aug 13, 2019 at 7:38 AM Andrew Kondratev
wrote:
> Hi!
>
> My colleague noticed some dodgy behavior, which I think could be a bug.
> Just asking here i
Hi!
My colleague noticed some dodgy behavior, which I think could be a bug.
Just asking here if it's known, befor I try to create a quickstart or PR.
* page is rendered
* user interacts with a page causing ajax request (clicking checkbox)
* the wicket PageAccessSynchronizer locks, renders and unl
