Re: [Cocoa-Java] Seeking some explanations around an NotSerializableException
Re: [Cocoa-Java] Seeking some explanations around an NotSerializableException
- Subject: Re: [Cocoa-Java] Seeking some explanations around an NotSerializableException
- From: Michael Hall <email@hidden>
- Date: Mon, 24 Jan 2005 19:30:49 -0600
On Monday, January 24, 2005, at 06:34 PM, Frédéric BLANC wrote:
Michael,
Just have your class implement the java.io.Serializable interface. (…)
It's something I've tried straight away; and it did seem to work
(since the sheet was going down again)... as long as I don't alter the
toolbar in any way.
For a long shot you could try serialver.
e.g. from Terminal
[black-box:~] mjh% serialver java.lang.String
java.lang.String: static final long serialVersionUID =
-6849794470754667710L;
Add that to the source for the class is supposed to give you some
protection for exceptions when the versions change. Basically you're
saying as long as it contains this don't give me those errors. Makes
you responsible for deciding if changes really should break backward
compatibility for serialization.
You should get an exception not a signal 11 so it would be a long shot.
Otherwise something involved must not be serializable in some weird way
and avoiding it as per Glen's earlier suggestion, using null or
transient. But first you have to figure out if you could isolate the
part having the problem and that would be trial and error at best
assuming you have full access to parts, possibly impossible if it's
done automagically where you don't have access.
Mike Hall <mikehall at spacestar dot net>
<http://www.spacestar.net/users/mikehall>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden