On Thu, Jul 22, 2010 at 4:11 PM, Johan Compagner <jcompag...@gmail.com> wrote: > what kind of classes are serialized constantly? > are those proxies or other generated onces? >
All sorts of stuff I guess. This doesn't necessarily happen on one particular page. It just starts happening after a while and the application just starts throwing these stack traces. > Somehow it has something to do with getting the default constructor of > the first none serializable class > And i think your first class in the hierarchy that is found that > doenst implement Serializable doesnt also have a default constructor > Then when that state is found it will generate a constructor method or > something (so some kind of quick asm wrapper class with that > constructor) > > So look at the classes that you serialize, find the first one that is > none serializeble and give it a default constructor. > (it could be that that default constructor needs to be private) > Man, where to begin. I'm going to look at my IDE to see if it has a code inspection for this! :) --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
