Sometimes I hate being a stickler... Section 5.5 of the JavaBeans Spec (http://java.sun.com/products/javabeans/docs/beans.101.pdf).....
Summary of persistence All beans must support either Serialization or Externalization. It is always valid for an application to save and restore the state of a bean using the Java Serialization APIs. (The serialization APIs handle both Serializable and Externalizable objects.) A tool may also use generated code to restore the state of a bean unless the bean has specified the "hidden-state" attribute, in which case the bean must be saved and restored with serialization and/or externalization. So I think the short answer is yes, in order to be a full-fledged JavaBean, you must implement Serializable (or its subinterface Externalizable), although the spec does seem to leave room for implementing some other custom mechanism in tools (like an IDE). Steve -----Original Message----- From: Craig R. McClanahan [mailto:craigmcc@;apache.org] Sent: Friday, October 18, 2002 2:03 PM To: Struts Developers List; [EMAIL PROTECTED] Subject: RE: WHY! Won't Form Classes Load On Fri, 18 Oct 2002, edgar wrote: > Date: Fri, 18 Oct 2002 17:03:32 -0400 > From: edgar <[EMAIL PROTECTED]> > Reply-To: Struts Developers List <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > To: 'Struts Developers List' <[EMAIL PROTECTED]> > Subject: RE: WHY! Won't Form Classes Load > > Isn't a requirement that beans be serializable anyway? > Not in the general sense of JavaBeans (although it is not uncommon). There are some circumstances where serializability is required (such as a value object being passed back and forth to an EJB). > Edgar Craig -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
