I don't know if this helps but I used to get similar problems with Tomcat. One of the items I was putting into the session wasn't Serializable. I fixed that (just implemented the Serializable interface) and I haven't seen any problems since on context reloading.
Yep. That's seems to be the problem. This is gonna be a tricky one ... Serialized objects by default want a default constructor. Components managed by pico (a) often don't have a default constructor and (b) are not allowed to have more than one constructor.
I've put in a temporary workaround in CVS that causes new instances of all the session scoped components to be created if the session is reloaded.
I'll see if the pico guys have any suggestions.
M
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
