Guten Tag Sven Meier,
am Mittwoch, 1. April 2020 um 21:09 schrieben Sie:
> Seems WebPageRenderer thinks it has to store the rendering result and
> redirect to it.
> That's definitely nothing something you want to have when using
> ComponentRenderer.
Agreed, but I couldn't find yet why it thinks s
Hi Thorsten,
I wanted to ask for that stacktrace anyway: )
Seems WebPageRenderer thinks it has to store the rendering result and
redirect to it.
That's definitely nothing something you want to have when using
ComponentRenderer.
There's probably something in your setup that triggers this redi
Guten Tag Sven Meier,
am Mittwoch, 1. April 2020 um 17:31 schrieben Sie:
> Without a quickstart it's hard to guess whether this is an error
> actually or you did something wrong.
Things are easy in my opinion: There's no session-ID in my use case at
all, the code itself is tolerant and many other
ll already.
Additionally I started using WicketTester in that project to test
things and during running tests I get the following errors logged:
16:31:21 ERROR
org.apache.wicket.protocol.http.WebApplication.storeBufferedResponse:
storeBufferedResponse needs a valid session id to store the
response, but
within ComponentRenderer as well already.
Additionally I started using WicketTester in that project to test
things and during running tests I get the following errors logged:
> 16:31:21 ERROR
> org.apache.wicket.protocol.http.WebApplication.storeBufferedResponse:
> storeBufferedResponse need
