[ https://issues.apache.org/jira/browse/WICKET-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495265 ]
Matej Knopp commented on WICKET-519: ------------------------------------ Sure we can do that. But thinking of it, there are so many simple ways of making the page no longer available in wicket (e.g add a obsolete flag and check it in onatach)... > remove page versions from the second level cache when explicitly removed > ------------------------------------------------------------------------ > > Key: WICKET-519 > URL: https://issues.apache.org/jira/browse/WICKET-519 > Project: Wicket > Issue Type: Bug > Components: wicket > Reporter: Eelco Hillenius > Assigned To: Johan Compagner > Fix For: 1.3 > > > Someone at Matej's session had an interesting question about how pages can be > removed from the history when you explictly want to avoid users being able to > go back to that version (i.e. expire them). Removing the page from the page > map works fine with the HttpSessionStore, but doesn't with > SecondLevelCacheSessionStore by the looks of it; FilePageStore#removePage > just removes from pending but once it is serialized to disk, it will always > be availalbe. I think this is wrong. An explicit call to PageMap#remove(Page) > should remove it from second level cache so that it is in effect expired. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.