Jon Stevens wrote:
> For some reason, I was reading your "should" as a "must" and that is not
> accurate. :-)
Sorry I overlooked that important bit ;-)
> I have been lobbying within JSR 053 to change it to say that *only* objects
> that are Serializable will be accepted because otherwise, there is no solid
> way (other than to log something) to notify the developer that they have
> lost their session as a result of a classloader reload or something like
> that but I haven't gotten real far yet so I was looking for ammo outside of
> the servlet spec (/me thinking that your statement of J2EE was some other
> document) that mandated that. :-)
Uh, the spec says that the servlet container can throw
IllegalArgumentException
if it doesn't like the object passed to setAttribute method (ie
application is
declared to be distributed and the object is not Serializable nor does
the
container know how to handle it otherwise). I think that it would notify
the
develper pretty well that something is wrong.
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
