On Wed, May 31, 2000 at 10:15:39AM -0700, Jon Stevens wrote:
> > Right I just looked at in the changes.html for JServ 1.1.1 it says that
> > "only objects which can be found in the system or bootstrap classpath
> > will be kept." Now AFAIK I *have* to put the Turbine jar in the
> > repositories classpath so that JServ can see the Turbine servlet, and
> > that means that TurbineUser etc are not 'found in the system or
> > bootstrap classpath' (I think - I'm not sure I fully understand
> > 'bootstrap' in this context).
>
> correct.
So session serialization doesn't work for TurbineUser with JServ...?
(unless I do something like take Turbine.class out of the jar and put it
alone in the repositories classpath, whilst the rest of the turbine jar
gets put in the system classpath).
> Jeff just sent me some info that will help...essentially the problem to
> solve is to make SURE that whatever is in the session can be serialized. One
> thing that seemed to be in his session was a PermissionSet object and it
> wasn't marked as serializable. So, I'm figuring that there is something else
> in there that can't be serialized and that is the problem. hopefully he will
> send me his code and i will work on this a bit today...
And this would stop the serialization working in JServ too, right?
--
Sean Legassick
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
