On 17-12-2008 at 16:43, epsilon wrote: > Is there any workaround to the following exception (using Tomcat): > > Caused by: java.io.NotSerializableException: > net.sourceforge.stripes.action.ActionBeanContext > > I never put my ActionBean in session, except that I'm using flash() with > RedirectResolution, which I believe is using session as its temporary storage. > During context reload or tomcat restart, tomcat will attempt to serialise and > deserialise all session objects, which includes any ActionBeans which have > been > put into sessions, which in turn has an ActionBeanContext. [...] > The main question here is, is there any workaround to enable me to reload my > webapp and do a restart on tomcat without getting the exception above, so I > can > have my sessions intact?
The easiest way would be to extend ActionBeanContext to rol your own. It can either be configured or used as an extension (my favorite approach). An implementation can be as simple as an empty class that implements java.io.Serializable and extends ActionBeanContext. I'm not sure though, how this affects code that tries to access the request, response or session from the context. I'm assuming it will work, because after a restart no application processes will be running (yet) unless started explicitly. Oscar -- ,-_ /() ) Oscar Westra van holthe - Kind http://www.xs4all.nl/~kindop/ (__ ( =/ () Don't let your boss fuck you; that's anti-capitalist. ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
