I would like to be able to analyze a particular Wicket page to determine where I might be using models incorrectly. The model behind the page is a very nested serializable object that is kept in a document cache. The idea is to use a loadable detachable model that will retrieve the object from the cache on load. However, I'm fairly certain that there are places where objects from within the object hierarchy are being used incorrectly. I'm assuming that this probably results in portions of the object getting serialized with the page. Are there any tools or logging that would let me see the serialized page in a readable format? I guess one way I could analyze the problem is to make my object unserializable and work through the errors. Any other ideas?
-- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Models-and-page-serialization-tp4663668.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
