Hah. Okay, I'm an idiot tonight. It looks like this was a JavaScript
cookie problem (not 100% sure though).
Jonathan Locke wrote:
>
>
> For whatever reason, this is 100% repeatable for me right now. The AJAX
> callback does NOT have a sessionid cookie.
>
>
> Jonathan Locke wrote:
>>
>>
For whatever reason, this is 100% repeatable for me right now. The AJAX
callback does NOT have a sessionid cookie.
Jonathan Locke wrote:
>
> This is a real bug in 1.3, it turns out, and I think it does not have
> anything to do with cookies or application servers.
>
> I have verified in an a
Could it be that the onload ajax request somehow comes back from the browser
before wicket creates the pagemap and binds it to the session?
Jonathan Locke wrote:
>
> This is a real bug in 1.3, it turns out, and I think it does not have
> anything to do with cookies or application servers.
>
>
This is a real bug in 1.3, it turns out, and I think it does not have
anything to do with cookies or application servers.
I have verified in an application getting this exception that the session id
is constant for every request (modified wicket to print it out).
The exception is begin thrown fr
What was the result of this vote? Is EmptyPanel going to be added to Wicket
1.3?
On 5/4/07, Jonathan Locke <[EMAIL PROTECTED]> wrote:
so i propose a vote to add this. i'm +1.