Re: session serialization

[Jon Stevens]

updated report:

ok, i have confirmed that the session serialization portion is working 100%
properly within Tomcat itself. In other words, the classloader gets
reloaded, the session object (with "turbine.user" in it) is serialized and
then de-serialized properly.

One more bit of oddness is that the dumpSession stuff that I'm calling from
within Turbine which dumps the session to a bytearraystream and then
attempts to de-serialize it right away is failing with ClassCastExceptions.
That is probably close to where the problem is.

If it isn't that, then I think the bug might be in Turbine itself now...

still digging.

-jon



------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]