I wouldn't do it, unless you use distributed sessions. Having serializable forms will cause tomcat to dump everything from the session to a file, and reload it after restart. Unless you explicitely want this (user-invisible restart, but then you need to make EVERYTHING serializable) it makes restarts unneccesary long and sessions quite unpredictable, especially in the development.
regards leon On 9/30/05, starki78 <[EMAIL PROTECTED]> wrote: > I don't know if you have to use implements at all > because > the super-class does already implement it. > What would you like to achieve? > > Regards Starki > > > > > ---------- Initial Header ----------- > > From : "Murray Collingwood" [EMAIL PROTECTED] > To : user@struts.apache.org > Cc : > Date : Fri, 30 Sep 2005 17:27:19 +1000 > Subject : Serializable > > > > > > > > > Just a quick question. > > > > Does anybody follow any rule (personal or corporate) for when to use > > "implements > > serializable" on a Struts form-bean? > > > > Kind regards > > mc > > > > > > FOCUS Computing > > Mob: 0415 24 26 24 > > [EMAIL PROTECTED] > > http://www.focus-computing.com.au > > > > > > > > -- > > No virus found in this outgoing message. > > Checked by AVG Anti-Virus. > > Version: 7.0.344 / Virus Database: 267.11.9/115 - Release Date: 29/09/2005 > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
