on 1/2/2001 1:45 PM, "Rafal Krzewski" <[EMAIL PROTECTED]> wrote:
>> It *could* but it doesn't *have* to. I was lobbying for a *have*.
>
> I agree... It should be changed to "must throw"...
>
> Rafal
I feel that way as well, but others disagree. :-) I think we agreed that the
wording would be changed to be something like this (this was my suggested
wording):
"In order to allow sessions to persist across class reloading within the
container, it is highly advised that you should implement the Serializable
interface. Otherwise, you risk the strong chance that the objects within
your session will not exist after the classloader has been reloaded."
I also believe that it should be documented that:
"If an object is not serializable AND it implements the
HttpSessionBindingListener interface, that the valueUnbound() method will be
called before the object is poofed into oblivion."
thanks,
-jon
--
Honk if you love peace and quiet.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
