Hello Wicketeers,
I am posting this question in the hope that some if the more knowledgeable
members of the wicket community can help me understand Wicket's
serialisation process and use of SessionStores, etc..
I have been tasked with overhauling a fairly old Wicket project and this
includes migrating from Wicket 1.3.8 to 1.6+. I have been migrating
incrementally and I'm now working my way to 1.5.12 compliance. The issue I
have encountered is as follows : in 1.3 a SecondLevelCacheSessionStore was
used with a DiskPageStore which had most of it's methods overridden and
either left empty or set to return null or false. The original programmer
left no indication of why this was done (I'm told there was a ‘valid’ reason
but no-one remembers and it would seem that this former colleague didn’t
believe in documentation and/or commenting).
This is an area of Wicket I've always left alone so consequently I have
little notion of what is actually happening here. I’d appreciate any
information about this aspect of Wicket as I’m having trouble finding online
resources which can spell this out. This would certainly bolster my Wicket
knowledge and help me understand what my predecessor was trying to achieve,
why, whether it’s still applicable and if need be how to port it to 1.5+.
Many thanks in advance,
C
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Migrating-SecondLevelCacheSessionStore-tp4668256.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
