You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sven Meier (Jira)" <ji...@apache.org> on 2021/11/12 22:53:00 UTC

[jira] [Resolved] (WICKET-6933) Ease use of InSessionPageStore as persistent store

     [ https://issues.apache.org/jira/browse/WICKET-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sven Meier resolved WICKET-6933.
--------------------------------
    Fix Version/s: 10.0.0
                   9.7.0
       Resolution: Fixed

The InSessionPageStore used by default for caching of the last page now uses a separate key. This way users will not have to take care of the key, if they use an additional InSessionPageStore as persistent store.

> Ease use of InSessionPageStore as persistent store
> --------------------------------------------------
>
>                 Key: WICKET-6933
>                 URL: https://issues.apache.org/jira/browse/WICKET-6933
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 10.0.0, 9.6.0
>            Reporter: Sven Meier
>            Assignee: Sven Meier
>            Priority: Minor
>             Fix For: 10.0.0, 9.7.0
>
>
> Using InSessionPageStore as persistent store, requires users to supply a separate key, to prevent interference with the InSessionPageStore instance used for caching of the last recently used page.
> Overriding #getKey() is easily forgotten, so it would be more convenient if the InSessionPageStore used for caching already used a separate key instead.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)