On Fri, 2006-03-31 at 19:55 -0500, Stuart Ballard wrote: > On 3/31/06, Andrew John Hughes <andrew@xxxxxxxxxxxxxx> wrote: > > I believe it's on the individual Javadoc pages for each Swing class e.g. > > on JComponent: > > > > 'Warning: Serialized objects of this class will not be compatible with > > future Swing releases. The current serialization support is appropriate > > for short term storage or RMI between applications running the same > > version of Swing.' > > Yuck, so there's no easy way to verify that it actually does apply to > *every* class in swing? Maybe a better solution in that case is to invent a "magic" serialVersionUID number that means "not-really-serializable" and tag all classes that are not guaranteed to serialize between different implementations/versions this way? It will be a bit more work then just excluding whole packages of course. But at least it is more accurate and can be used also in other situations. Cheers, Mark -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 191 bytes Desc: This is a digitally signed message part Url : http://developer.classpath.org/pipermail/classpath/attachments/20060401/0d2c5439/attachment.pgp
