Unfortunately, this does not answer my question. Tom
On 11.08.2010 09:57, Johan Compagner wrote: > then you just have to check where those classes are used and where > they could be stored in a wicket component/model > and make sure you detach that object . > Wicket tells you the field hierarchy to that object so you should be > able to track it down quite easily > > > On Wed, Aug 11, 2010 at 09:55, Thomas Singer <wic...@regnis.de> wrote: >>> doesnt the message of that exception tell you which object class is the >>> problem? >> >> It does, but I don't want to make the logged class serializable, but instead >> avoid it. Independent of that I want to verify whether the done steps work >> correctly. >> >> Tom >> >> >> On 11.08.2010 09:27, Johan Compagner wrote: >>> doesnt the message of that exception tell you which object class is the >>> problem? >>> >>> >>> On Wed, Aug 11, 2010 at 09:24, Thomas Singer <wic...@regnis.de> wrote: >>>> Hi, >>>> >>>> In our server logs we have a couple of WicketNotSerializableException >>>> logged, but we don't know when they occur. How we can create them locally >>>> in >>>> our development environment (to test whether we have avoided them)? >>>> >>>> Thanks in advance, >>>> Tom >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
