Any way you could force use of PropertyResourceBundle instead, and then
write a simple "save this to a java.util.Properties" converter? Then
MessageResources (or whatever the name of the class is) could have an
easy writeExternal() method that effectively makes it serializable.
Product of two seconds of thought, so #include <appropriate_warnings.h>.
Cheers,
Laird
----- Original Message -----
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 07, 2000 2:31 PM
Subject: Re: java.io.NotSerializableException: Serialization problems
running Struts on Weblogic
> "Punyansky, Alex" wrote:
>
> > Hi,
> >
> > We created an application based on struts and are trying to deploy
it on
> > Weblogic 6.0 beta2. Looks like Weblogic doesn't look at
<distributable /> in
> > web.xml and requires all classes that can be used as context
attributes to
> > be serializable. We tried to make MessageResources and ErrorMessages
classes
> > implement Serializable but we still get the following Exception:
> >
>
> Also, the Serializable restriction when you specify <distributable/>
relates to
> *session* attributes, not *context* attributes. Requiring context
attributes to
> be serializable is a platform-specific restriction that WebLogic is
imposing. I
> will look into the issues for the Struts-related classes, but it looks
to me
> like the JDK's ResourceBundle class is not Serializable :-(.
>
> NOTE: The current design of the Struts example application means it
would not
> work correctly in a real distributable environment anyway, because the
> pseudo-database is stored in memory as a servlet context attribute.
>
> Craig McClanahan
>
>
>
