You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Frank Bille Jensen (JIRA)" <ji...@apache.org> on 2007/12/09 12:21:43 UTC
[jira] Updated: (WICKET-331) Session#clear() does not work - no
pages are removed from the session
[ https://issues.apache.org/jira/browse/WICKET-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Bille Jensen updated WICKET-331:
--------------------------------------
Fix Version/s: (was: 1.3.0-rc2)
1.3.0-rc1
> Session#clear() does not work - no pages are removed from the session
> ---------------------------------------------------------------------
>
> Key: WICKET-331
> URL: https://issues.apache.org/jira/browse/WICKET-331
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.0-beta1
> Reporter: Martin Benda
> Assignee: Johan Compagner
> Fix For: 1.3.0-rc1
>
>
> The method wicket.Session#clear() should remove all pages from the session but it does not!
> The bug is in wicket.PageMap: the final methods visitEntries(...) and getEntries() assume that pages are stored as session attributes (with a name prefixed "p:"). But the PageMap implementation which is used by default - SecondLevelCacheSessionStore$SecondLevelCachePageMap - uses IPageStore insted of session attributes. As a result, the inherited method visitEntries does not visit any entry and no entry is removed from the page map when PageMap#clear() is called.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.