Hi Sven, Thanks a lot for the quick reply!
Are you sure the code in GaePageManagerProvider is correct? Don't we end up with two instances of InSessionPageStore in this case? Once as `newSessionStore` and once as `newPersistentStore`? The resulting chain looks like this: RequestSore -> *InSessionStore* -> AsynchronousStore -> SerializingStore -> CryptingStore -> *InSessionStore* Best, Thomas On Mon, Apr 22, 2019 at 10:57 PM Sven Meier <s...@meiers.net> wrote: > Hi Thomas, > > many thanks for testing so early! > > Set a custom provider of the page manager, see wicketstuff's > gae-initializer as an example: > > application.setPageManagerProvider(new > GaePageManagerProvider(application, maxPages)); > > > https://github.com/wicketstuff/core/blob/master/gae-initializer-parent/gae-initializer/src/main/java/org/wicketstuff/gae/GaePageManagerProvider.java > > Have fun > Sven > > > Am 22.04.19 um 18:47 schrieb Thomas Heigl: > > Hi all, > > > > I just experimentally upgraded my application to 9.0.0-M1. Most things > are > > straight forward, but I'm struggling with replicating my current page > > manager configuration using the new API. > > > > My current configuration for Wicket 8 looks like this: > > > > setPageManagerProvider(new DefaultPageManagerProvider(this) { > >> @Override > >> protected IDataStore newDataStore() { > >> return new HttpSessionDataStore(getPageManagerContext(), new > >> PageNumberEvictionStrategy(10)); > >> } > >> }); > > > > What is the Wicket 9 equivalent of this? > > > > Thanks, > > > > Thomas > > >
