As Craig says, the static state doesnt affect Serialization. When deserialized, the static state will be effectively borrowed from the JVM it is running in. As the classes concerned (abstract class ModuleConfigFactory, and interface ModuleConfig) do not have any instance state, we can just mark them Serializable (i.e. ModuleConfigFactory implements Serializable, ModuleConfig extends Serializable). Wouldn't it be better to enforce the Serializability at the interface/abstractClass level, rather than the implementation level? Mohan David Graham <[EMAIL PROTECTED]> wrote:Maybe it's not required. I'll look into it tommorrow.
Thanks, David >From: "Craig R. McClanahan" >Reply-To: "Struts Developers List" >To: Struts Developers List >Subject: Re: cvs commit: jakarta-struts/src/share/org/apache/struts/config >ModuleConfigFactory.java >Date: Mon, 3 Feb 2003 19:21:24 -0800 (PST) > > > >On Mon, 4 Feb 2003 [EMAIL PROTECTED] wrote: > > > Made log instance transient > >Is this actually required to achieve serializability? It was my >understanding that static variables were not part of the serialized state >of an object, so it shouldn't make any difference -- and it is guaranteed >to cause problems if the class were to be serialized and deserialized, and >then tried to log something. > >Craig > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------- Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now
