wicket-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Retzlaff (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WICKET-4286) ListView causes page ID increment
Date Fri, 16 Dec 2011 19:20:31 GMT

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

Dan Retzlaff commented on WICKET-4286:

There are two concepts here: "touched" pages and "dirty" pages. Simply retrieving a page from
the page manager "touches" it, scheduling it for serialization into the page store at the
end of the request. The question is whether it updates the original page store entry, or goes
into a new entry. The page gets a new page map entry if and only if it is marked "dirty" which
is triggered by component hierarchy change, component model change, or explicitly with Page#dirty().
However, WebPage#dirty() has a special case which prevents AJAX requests from *ever* marking
a page dirty.

So after the request that originally created your wizard's page, there must be another non-AJAX
request which dirties the page and advances its identifier past the one in the browser address
> 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
> 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


View raw message