From my own testing ... Blah blah Hey Jim that's all I need,
your testing I only experienced problems with read/writeUTF and not with writeObject and to be totally hunst the Object members for my class can never be null. I will take note of your test for future references
In any case, I can see that this area is a bit murky
and we need some arm twisting. I guess we can call it creativity
Another solution for this problem is to simply make sure that you String(s) are never null.
What I did in the constructor was this:
Which leads me to another (simple) question:
Given the above, the setXXX methods of the class should also have the same approach. Thinking in the constructor is it better to leave the code as is or call it's setXXX method as in:
Thanks so much for your help, Jim
[ October 09, 2003: Message edited by: Leslie Chaim ]