SCJP 1.4 SCWCD 1.4
Originally posted by Colin Fletcher:
> ...attribute values that implement java.io.Serializable will be transferred to the new JVM.
>[container] does not guarantee the object will retain its values in the new JVM.
>Spec:
Developers are not guaranteed that containers will call readObject and writeObject methods on session attributes if they implement them, but are guaranteed that the Serializable closure of their attributes will be preserved.
P.Dunn<br />SCJP, SCJD, SCEA & SCWCD
SCJP 1.4 SCWCD 1.4
The distributed servlet container must support the mechanism necessary for migrating objects that implement Serializable.
Developers are not guaranteed that containers will call readObject and writeObject methods on session attributes if they implement them, but are guaranteed that the Serializable closure of their attributes will be preserved.
SCJP 1.4 SCWCD 1.4
Developers are not guaranteed that containers will call readObject and writeObject methods on session attributes if they implement them, but are guaranteed that the Serializable closure of their attributes will be preserved.
SCJP 1.4 SCWCD 1.4
SCJP 1.4 SCWCD 1.4
Originally posted by Colin Fletcher:
The way I handled this was to implement both Serializable and httpSessionActivationLitener interface... the listener just called read/write object..
SCJP 1.4 SCWCD 1.4
Originally posted by Jose Esteban:
This DOESN'T mean that the attributes will not conserve their values; it ONLY MEANS that the readObject and writeObject methods on these attributes could not be called.
P.Dunn<br />SCJP, SCJD, SCEA & SCWCD
Politics is a circus designed to distract you from what is really going on. So is this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
|