On Mon, Mar 26, 2012 at 1:12 PM, Bas Gooren wrote:
> Hi,
>
> Op 25-3-2012 18:59, schreef Martin Grigorov:
>>
>> On Sun, Mar 25, 2012 at 7:19 PM, Bas Gooren wrote:
>>>
>>> https://issues.apache.org/jira/browse/WICKET-4468
>>
>> Thanks!
>> We will consider it.
>>
>>
>>> Ok: here's whats happening:
Hi,
Op 25-3-2012 18:59, schreef Martin Grigorov:
On Sun, Mar 25, 2012 at 7:19 PM, Bas Gooren wrote:
https://issues.apache.org/jira/browse/WICKET-4468
Thanks!
We will consider it.
Ok: here's whats happening:
- A request comes in for /login
- WebPageRenderer:264-266 stores the buffered resp
On Sun, Mar 25, 2012 at 7:19 PM, Bas Gooren wrote:
> Hi,
>
> Op 25-3-2012 17:44, schreef Martin Grigorov:
>
>> Hi,
>>
>> On Sat, Mar 24, 2012 at 10:44 PM, Bas Gooren wrote:
>>>
>>> After more debugging, I learned some new things about wicket.
>>>
>>> It appears that an invisible stateful link mak
Hi,
Op 25-3-2012 17:44, schreef Martin Grigorov:
Hi,
On Sat, Mar 24, 2012 at 10:44 PM, Bas Gooren wrote:
After more debugging, I learned some new things about wicket.
It appears that an invisible stateful link makes a page stateful.
The base page for this application contains a username labe
Hi,
On Sat, Mar 24, 2012 at 10:44 PM, Bas Gooren wrote:
> After more debugging, I learned some new things about wicket.
>
> It appears that an invisible stateful link makes a page stateful.
> The base page for this application contains a username label + logout link
> (stateful), which are in a W
After more debugging, I learned some new things about wicket.
It appears that an invisible stateful link makes a page stateful.
The base page for this application contains a username label + logout
link (stateful), which are in a WebMarkupContainer which is invisible if
the user is not logged i
Martin,
Thanks for your pointer.
This is indeed the reason for the loop: no buffered response is found.
Something must have changed between 1.5.0 and 1.5.1 regarding (session)
cookies and continueToOriginalDestination(), since it is no longer
setting a session cookie.
For all our public-faci
Hi,
A hint for debugging: the request to login?0 should be handled by
org.apache.wicket.core.request.mapper.BufferedResponseMapper not by
WebPageRenderer. Check why there is no stored response.
A suggestion: try to make your login page stateless. Otherwise every
hit to your application will creat
We have the following simple setup:
BasePage checks if user is logged in, if not (and this is not the
LoginPage), RestartResponseException(LoginPage.class);
LoginPage extends BasePage; contains a form to login;
The application runs in the root context.
Now on 1.5.0 this works like a charm;
A
