See for example SerializableChecker. It does the same - checks that a serialized object implements java.io.Serializable. If it doesn't then it prints a nice message explaining where this object is used.
Martin Grigorov Wicket Training and Consulting On Wed, Jan 15, 2014 at 6:29 PM, gmparker2000 <greg.par...@brovada.com>wrote: > Thanks for the tip. I'm a little unclear on what this is telling me > though. > Wouldn't this just tell me if the detach method of all my LDMs was called? > What I'm interested in determining is where my LDMs are directly > referencing > objects that will inadvertantly get serialized with the LDM. For example, > if an LDM has a member variable pointing to an object or the LDM accesses a > final variable from its parent class. I want to be sure I'm not > serializing > business objects or references to business objects along with the page. > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Models-and-page-serialization-tp4663668p4663746.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 > >
