Hi Jonathan,
developing against a recent trunk I made a strange obeservation which
might be connected to this.
I have a page with several wicketAjaxGet calls. Some of em work fine.
The others behave strange, if clicked/called right after the page was
loaded they are answered with a Page Expired. If called after some other
fine working ones were called, those strange ones behaved just as expected.
Loading the page wicket complained with a:
ERROR org.apache.wicket.RequestCycle - the requested resource was not found
org.apache.wicket.WicketRuntimeException: the requested resource was not
found
at
org.apache.wicket.util.resource.WebExternalResourceStream.getInputStream(WebExternalResourceStream.java:99)
The page was delivered to the client without any warnings on the client
side.
The missing resource was a 'style.css'.
After I took care of that the Page worked fine, all wicketAjaxGet calls
worked as expected.
BTW, could someone please take care of:
https://issues.apache.org/jira/browse/WICKET-582
Debugging the problem I noticed that Page Expired was given cause of
line 114 in WebRequestCycleProcessor:
// the page is no longer the active page
// - ignore this request
processRequest = false;
Beyond this a breakpoint on AccessStackPageMap [line: 284] - put(Page)
showed that on initial load of the page the page itself was put on the
AccessStack and right after this an ExceptionErrorPage was put on that
stack.
The ExceptionErrorPage.id was the page.id incremented by one.
And this is the point were I got lost. Maybe someone else has a better
overview.
Martin
Jonathan Locke schrieb:
> Did we find a resolution for this yet? We are having the same problem in
> Wicket 1.3 trunk and I'm about to start investigating. Any definite
> information or conclusions (whether complete or not) would be very much
> appreciated.
>
>
> Andrew Berman wrote:
>
>> I am having a strange issue. If I access my site for the first time (I
>> clear all cookies, sessions, and cache before going to the site), the page
>> comes up fine. However, if I click one of the AJAX links, I get a page
>> expired error. Any thoughts why this is happening? I see it create a new
>> session and the cookie, but it looks like the Ajax link is not valid for
>> some reason. I am using Wicket 1.2.6. Any thoughts?
>>
>> Thanks for any help,
>>
>> Andrew
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/
>> _______________________________________________
>> Wicket-user mailing list
>> Wicket-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wicket-user
>>
>>
>>
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
