Re: Proper way to deal with serialization of session attribute with Logger attribute

2003-05-27 Thread Micael
At 12:31 PM 5/27/03 -0500, you wrote: Normally, loggers should be created as class static variable which are, effectively, transient already. Why would you want instance loggers anyway? Loggers are thread safe. Just make it static. You can deal with creating a new logger in the readObject()

Re: Proper way to deal with serialization of session attribute with Logger attribute

2003-05-27 Thread Jacob Kjome
Normally, loggers should be created as class static variable which are, effectively, transient already. Why would you want instance loggers anyway? Loggers are thread safe. Just make it static. You can deal with creating a new logger in the readObject() when the object is deserialized. Jake

RE: Proper way to deal with serialization of session attribute with Logger attribute

2003-05-27 Thread Shapira, Yoav
Howdy, It's dangerous to stick class objects in a session object as attributes, precisely for these serializable type problems. The transient approach should be fine. I would skip the checking if its null or not in every accessor method. The static initialization is still reliable for transient