Forwarded message from Jon Zeppieri <[EMAIL PROTECTED]> Brian
There are a few, small issues like these in the util classes I wrote. I think that some of them have a lame-brained clone() as well. Very easy to fix. Unfortunately, since the FSF adopted draconian security measures (for very good reasons, I understand), I haven't had access to CVS. Also, this message will not make it to the Classpath list, due to tricks my MTA (or maybe it's my MUA) likes to play on me. My username on the mail server does not match my username on my own computer, and all of my mail is sent from my computer's username -- which, of course, is not *on* the Classpath list. So, uh, could one of you forward this to the list if you feel it is worthwhile? Thanks. -jaz Brian Jones wrote: > > Artur Biesiadowski <[EMAIL PROTECTED]> writes: > > > For now java.util.ArrayList (and I suppose a lot of other classes) is > > not compatible with one serialized from JDK because of different > > serialVersionUID. ArrayList do not seem to have published it's ID, so it > > is probably computed in normal way from name/fields. > > > > Could we legally check serialver for JDK class library and include their > > IDs in classpath classes ? Also, are there any other reasons to not do > > it ? > > The serialVersionUID for each class should match Sun's reference > implementation in lieu of documentation. I think java.lang should be > okay though I don't know the status of the rest of the packages on this. > > Brian > -- > Brian Jones <[EMAIL PROTECTED]>
-- Brian Jones <[EMAIL PROTECTED]>
