Hey Bas,
First of all thanks for debugging and for your explanation.
I had to dig a bit in the Git history, but the purpose of the zero-args
constructor was to provide an entrypoint for a (now defunct) Selenium test
suite to see if the error page rendered correctly.
Either way, both of your solu
Thanks!
On Fri, Nov 12, 2021 at 7:02 AM Maxim Solodovnik
wrote:
> WicketStuff core 9.6.0 based on Apache Wicket 9.6.0 is released
> and soon will be available at Maven Central!
>
> The changelog is:
>
> Maxim Solodovnik (7):
> Switching to the next development version
> Cometd versio
WicketStuff core 9.6.0 based on Apache Wicket 9.6.0 is released
and soon will be available at Maven Central!
The changelog is:
Maxim Solodovnik (7):
Switching to the next development version
Cometd version is increased
javadocs are partially fixed
Wicket is updated, link t
Hi Jeroen,
I just gave your quickstart a spin.
After some debugging I see that this is what happens: because you set the
redirect mode to ALWAYS_REDIRECT, wicket needs to generate a target url to
redirect to.
It determines if the page is stateless (in your case: yes), can be created
from a bookma
Our application uses an implementation of IRequestCycleListener to redirect
users to a custom error page with contextual information (which includes a
reference to an external bug tracking system).
When the target page is also mounted in the application, we are seeing
rather unexpected behavior: t
Indeed, flush-before-detach (WICKET-6831) was a huge performance
improvement.
Sven
On 11.11.21 08:55, Korbinian Bachl wrote:
Hi Sven,
thanks a lot!
I've looked into that GaePageManagerProvider and adapted it myself. However,
during test I somehow observed that the reason why I did use the
