Description
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.
Attachments
Issue Links
- is related to
-
WICKET-6769 InMemoryPageStore customizable map implementation
- Resolved
-
WICKET-6766 Keep page ids in tests like they where in Wicket 8
- Resolved
- relates to
-
WICKET-6933 Ease use of InSessionPageStore as persistent store
- Resolved
- mentioned in
-
Page Loading...