Pat,
Thanks, I was made aware of the restart option by SS support. Cycling the
SS server is not an option I like during development nor during production.
The restart of SS takes a long time during dev and I prefer not to disrupt
my production server in such a manner.
It sounded as though there were plans to come up with a serializable version
of the class in question. Is this still in the works?
TIA,
Bill Pfeiffer
----- Original Message -----
From: "Ludwig, Pat" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 02, 2001 1:15 PM
Subject: RE: SilverStream 3.7 and Struts
> Bill,
> the non-serializable nature of MessageResources is a likely cause for your
> problem. even if your app doesn't use MessageResources, Struts itself
does.
> if this is the cause of your problem, cycling the Silverstream server
should
> resolve it.
> regards,
> Pat Ludwig
>
> -----Original Message-----
> From: Bill Pfeiffer [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 02, 2001 7:48 AM
> To: Struts-User
> Subject: SilverStream 3.7 and Struts
>
>
> There was some mention a while back in a thread titled "Proposed Solution
to
> Non-Serializable MessageResources Class" that described a problem that I
am
> encountering with SilverStream 3.7. I am not actually using
> MessageResources in my web application, but I am encountering the
following
> when deploying a very simple struts web app to SilverStream:
>
> java.lang.LinkageError: Class org/apache/struts/action/ActionForm violates
> loader constraints
>
> SilverStream support indicated that this had something to do with the way
> the MessageResources is not serializable.
>
> Is there an update (Struts or SilverStream) that addresses this problem?
>
> TIA,
>
> Bill Pfeiffer
>
