[
https://issues.apache.org/jira/browse/WICKET-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794877#comment-16794877
]
Martin Grigorov commented on WICKET-6563:
-----------------------------------------
I've just tested my application that I use for Wicket trainings with
9.0.0-SNAPSHOT from master and WICKET-6563 branches and I didn't find any
issues.
To be able to do this I've upgraded wicket-jquery-selectors, wicket-webjars and
wicket-bootstrap projects to Wicket 9.0.0-SNAPSHOT.
Good work!
> Rework page and data storage
> ----------------------------
>
> Key: WICKET-6563
> URL: https://issues.apache.org/jira/browse/WICKET-6563
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 9.0.0
> Reporter: Sven Meier
> Assignee: Sven Meier
> Priority: Minor
> Fix For: 9.0.0
>
>
> IPageManager, IPageStore and IDataStore are riddled with complicated and
> error-prone code aiming to do one simple thing: keeping pages around.
> There are multiple problems with the current implementation:
> * PageStoreManger does too muchÂ
> ** it handles request and session storage
> ** it contains workarounds for DiskDataStore, when the sessionId changes
> * IPageStore/AbstractPageStore
> ** has no access to IPageManagerContext
> ** juggles with byte[], serialization and conversion
> * IDataStore introduces an unncecessary third layer into the API
> Additional or specialized stores are difficult to implement.
> We should rework that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
