Can't you also mark your members as transient if you don't want them serialized? So shouldn't a combination of Serializable and transient properties also meet the requirement for serializing the object itself? Just curious if anyone is even using the transient keyword...
Thomas Gideon Sr. Software Developer B2eMarkets 301.230.2236 Tel. 301.230.2248 Fax. [EMAIL PROTECTED] www.B2eMarkets.com > -----Original Message----- > From: Eddie Bush [mailto:ekbush@;swbell.net] > Sent: Monday, October 28, 2002 11:26 AM > To: Struts Users Mailing List > Subject: Re: Serialization question... > > > Does the form contain any fields which do not implement Serializable? > If so that makes the form unable to be serialized. In order for an > object to be serializble both that object and *all* fields it > contains > *must* implement Serializable. It cascades too, so the > fields' fields > (if they are not simple types) must implement Serializable - and so > forth. Is this your problem, perhaps? > > Ryan Cornia wrote: > > >In my web application, I have all of my forms declared as - > > > >public final class <FORM_NAME> extends > >org.apache.struts.validator.ValidatorForm implements Serializable { } > > > >In my tomcat 4.1.12 logs, however, I keep getting errors - > > > >"Cannot serialize session attribute <FORM_NAME>...." > > > >Do I need to write a serialization function for each form? I assumed > >this was taken care of in org.apache.struts.validator.ValidatorForm. > > > >Thanks, > >Ryan > > > > > > -- > Eddie Bush > > > > > -- > To unsubscribe, e-mail: > <mailto:struts-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: > <mailto:struts-user-help@;jakarta.apache.org> > -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
