Hi Ed,

OK, I've just had a look at the attachments, and I don't see any
obvious problems.

Because JOS behaves the same as JSX, it sounds like a bug in the code
in the UI classes that customize their serialization (either for
writing or reading). I suggest checking Sun's bug parade - they often
have workarounds, too.

It's very odd that XMLEncoder also fails - one commonality is your own
code, although normally this wouldn't cause serialization issues. But
do you subclass any UI components? It could be that such a subclass
must handle serialization in some way. A careful scan of the javadocs
should reveal this (esp the "serial form", hyperlinked just before the
constructors, methods etc are listed). But I think this is unlikely,
unless you are changing some UI fundamentals.

The XMLEncoder problem is also worth checking out in the bug parade.

Apart from that, I can only offer the old path of narrowing down the
problem, by methodically removing things one at a time, until the
problem goes away. If nothing else, it might reveal a workaround.

Let me know how you go.


cheers,
Brendan