[WICKET-6563] Rework page and data storage

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 9.0.0-M1
• Fix Version/s: 9.0.0-M1
• Component/s: wicket
• Assignee: Sven Meier
• Reporter: Sven Meier
• Created: 23/Jun/18 16:49
• Updated: 10/Nov/21 21:10
• Resolved: 24/Apr/19 17:18

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.

Issue Links

• is related to: WICKET-6769 InMemoryPageStore customizable map implementation
• is related to: WICKET-6766 Keep page ids in tests like they where in Wicket 8
• relates to: WICKET-6933 Ease use of InSessionPageStore as persistent store
• mentioned in: Page Loading...