Hm, I'm not sure if I am interested in venturing into these waters. The
email I sent was about making sure I understaood how things are done
today: DataSource implementations implement Serializable and define
compatibility requirements in the form I described.
I think the ideas of using Referenceable or writing our own custom
serialization code are interesting, but it's not my itch to scratch
right now (unless it's required as part of solving the itch I have to
provide a custom classloader).
David
Bernt M. Johnsen wrote:
Additional comment to Øyvinds:
If we are to make these objects (or other objects in Derby)
Serializable *AND* backward compatible we should not pose restrictions
on how they are implemented like you suggest. Instead, custom
serialization should be used (by means serial version UID and
writeObject/readObject or writeReplace/readResolve). On the pitfalls
of serialization, i recommend Chapter 10 in Jushua Bloch's "Effective
Java".
begin:vcard
fn:David W Van Couvering
n:Van Couvering;David W
org:Sun Microsystems, Inc.;Database Technology Group
email;internet:[EMAIL PROTECTED]
title:Senior Staff Software Engineer
tel;work:510-550-6819
tel;cell:510-684-7281
x-mozilla-html:TRUE
version:2.1
end:vcard
