> not really sure what you mean or why you would have to do that. what is the
> usecase for having something that is not serializable in session?

As I trace this issue through my code it's becoming apparent that since
pages are added to the session any properties that is in a page that
isn't serializable causes the error. So it's not that I want to store
non-serializable things in the session necessarily. Many of my pages use
third-party libraries that are not serializable and these seem to cause
the issue.

I'll admit I'm a new comer so I may be missing something or violating a
Wicket principle as I build out my app.

> the debug feature serializes immediately so you get the error now
> instead of whenever the servlet container tries to replicate your session
> for you - at which point you will get a very similar error.

Thank you for this!

-S2
-- 
Steve Moitozo II

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to