Hi Sven,
thanks a lot!
I've looked into that GaePageManagerProvider and adapted it myself. However,
during test I somehow observed that the reason why I did use the HTTPSession
store some long time ago (wicket 1.5/6?) doesn't seem to be existing anymore.
Reason was that the underlying storage
Hi Korbinian,
> it was a real breeze. I'm very impressed!
thanks, glad to hear that.
You application is persisting pages in the Http session instead of disk.
Essentially what the wicketstuff's gae-initializer does too:
https://github.com/wicketstuff/core/blob/master/gae-initializer-parent/ga
Hi,
Im currently migrating our applications from wicket 8 to wicket 9.6 and so far
it was a real breeze. I'm very impressed!
One thing however that puzzles me is the following code I had in the
application init();
setPageManagerProvider(new DefaultPageManagerProvider(this) {
prote
