Matthew Heaton wrote:
> The example application itself doesn't put non Serializable objects into the
> Http session but all throughout the struts code non Serializable objects are
> placed in the PageContext with a scopes of Application, Page, or Request.
> It appears that Weblogic 6.0 beta may be handling these as if they were
> placed with a Session context and disallowing non serializable objects.
> Whatever is going on it also appears WL is enforcing this rule in non when
> <distributable> is not set.
>
Yep. Looking more closely at the error message, it is complaining about a
non-Serializable *context* attribute, not a *session* attribute. I, like
others, jumped to the wrong conclusion there.
The spec provides no prohibitions on this -- only a warning that you cannot use
a context attribute to share information globally in your application (the way
that the example app does with its pseudo-database) in a distributed
environment.
Is there by chance some WebLogic specific configuration property you have set
that makes it think this (or maybe all) applications should be treated as
distributable?
>
> -Matt
>
Craig
