In my java app I'm trying to serialize a JTree. JTree implements Serializable so that's an OK think to do, but when I do it I get an exception saying that CUIAquaTree is not serializable (about 20 frames below my call to writeObject).
So my question is What's up with that?
Is there a rational explanation for that or is it a bug?
In general there are a number of swing widgets that claim to be serializable (because they implement the interface) but are in fact not (because they fail on non serializable sub parts.)
This works fine on windows and linux and solaris so I expected it to work here.
I'm using eclipse and jdk 1.5 and 1.6. The both fail the same way.
Can anyone think of a work around for lying non serializable classes?
Thanks for any help.
So my question is What's up with that?
Is there a rational explanation for that or is it a bug?
In general there are a number of swing widgets that claim to be serializable (because they implement the interface) but are in fact not (because they fail on non serializable sub parts.)
This works fine on windows and linux and solaris so I expected it to work here.
I'm using eclipse and jdk 1.5 and 1.6. The both fail the same way.
Can anyone think of a work around for lying non serializable classes?
Thanks for any help.