[WICKET-6177] Introduce AsynchronousPageStore

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 7.4.0
• Fix Version/s: 8.0.0-M6
• Component/s: wicket
• Labels: serialization
• Environment: any
• Flags: Important
• External issue URL: https://issues.apache.org/jira/browse/WICKET-5805
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Martin Terra
• Created: 05/Jun/16 07:42
• Updated: 15/Nov/20 19:20
• Resolved: 12/Apr/17 21:32

Description

We have a performance issue with our Wicket app, page serialization causes inconvenience to user because PageStoreManager.storeTouchedPages() blocks the request until pageSerializer.serialize(page) has been handled.

Could this be solved by serializing the page in a separate thread and let the request complete?

The problem we have is that user is making quick small ajax modifications to the page but serialization + network latency makes the delay very inconvenient. If serialization could be done in separate thread, user would feel only the network delay which is bearable.

Issue Links

• causes: WICKET-6607 NoSuchMethodError when using Spring-Beans with constructor injection in an AjaxLink#onClick
• links to: Discussion at dev@
• links to: GitHub Pull Request #212
• mentioned in: Page Loading...