the only way to do this is as i described look where the exception really comes from and go to that same page in your developer, do as your user does. There is no other way, you really need to be in the same state.
On Wed, Aug 11, 2010 at 13:24, Thomas Singer <wic...@regnis.de> wrote: > I want to know how I can generate this exception in my development > environment. It is nasty to test on the production system. > > Tom > > > On 11.08.2010 10:53, Johan Compagner wrote: >> why not? >> if you know which page it was and which component/model that holds >> that none serializable class >> then you just have to make sure that you go to that same area in your >> developer.. >> What else do you expect that you can do? > > --------------------------------------------------------------------- > 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
