Hi, what is the current 'proper' way to debug serialization issues in Wicket?
My web search led me to two things: - Wicket contains SerializableChecker class whose explicit purpose is to assist in tracking down serialization issues. - At some point it seems that in development mode Wicket used to serialize pages on each request (so that you'll catch your serialization issues early). However right now it seems that Wicket is using SecondLevelCacheSessionStore for serialization purposes -- and the implementation does not make use of SerializableChecker. Also current Wicket apparently does not serialize pages on each request in development mode (at least not by default). So with the current Wicket is there a way to force page serialization on each request and to enable serialization debugging via SerializableChecker or something else? I'm asking because to track down my serialization issue recently I had to basically copy-paste SecondLevelCacheSessionStore and manually add SerializableChecker invocation to track it down. Plus the error only became apparent when Tomcat was shutdown with 'proper' sessions still in memory. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
