[ 
https://issues.apache.org/jira/browse/WICKET-4286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169562#comment-13169562
 ] 

Dan Retzlaff commented on WICKET-4286:
--------------------------------------

Thomas, it sounds likely. Look at the AJAX URLs to see if they're targeting a 
different page version than in the URL. Note that AJAX requests themselves 
don't advance the page identifier (see WebPage#dirty(boolean)), but for example 
normal reloads containing ListViews will. So maybe you can workaround the issue 
in your wizard by identifying and suppressing the non-AJAX, page-dirtying 
operation.
                
> ListView causes page ID increment
> ---------------------------------
>
>                 Key: WICKET-4286
>                 URL: https://issues.apache.org/jira/browse/WICKET-4286
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.3
>         Environment: any
>            Reporter: Mark Lichtenberg
>         Attachments: ajaxtest1.5.3.tar.gz
>
>
> A ListView with setReuseItems(false) causes the page ID to increment when the 
> page is reloaded or the back button is pressed. This new ID is not reflected 
> in the URL so Ajax actions against the new ID are lost when navigating away 
> and back again. 
> Steps to reproduce in quickstart
> 1) Load quickstart project in browser
> 2) Click "Link to Other" then click browser's back button.
> 3) Notice the log statement indicates the HomePage ID is 2, yet the URL 
> remains at ID 0
> 4) Click "Ajax Increment Link" a few times
> 5) Click "Link to Other" then click browser's back button
> 6) Notice the counter is at zero, and subsequent clicks to the "Ajax 
> Increment Link" start from zero. The current page ID output in the log is 4.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to