Am 20.08.2011 00:04, schrieb Sebastian Sickelmann:
Am 19.08.2011 23:21, schrieb Alan Bateman:
Sebastian Sickelmann wrote:
OK. We need to change the serialversion. But is this enough? May we
break applications out there which serialized
NoSuchMechanismExceptions or extended classes? I have compiled it
with no explicit serialversionUID and started
./serialver javax.xml.crypto.NoSuchMechanismException
to show the generated serialversionUID. The new is
4170396067457259019L.
I don't have time to send a detailed reply on this now but we can't
change the serialVersionUID.
-Alan.
In normal closed Application Development you only ensure to mark the
serialization incompatible and ready.
If you need to store objects most developers are doing custom
xml-serialization (because peak brackets(translated from german term
of abuse for <>) are so sexy :-( ).
I think i know what you mean and how to solve it.
I think you mean somethink like this:
http://download.oracle.com/javase/7/docs/platform/serialization/spec/version.html
I was always interessted into how to make serialized object realy
versioned in a way designed for the jvm.
I will read this tomorrow and try to fix the changed
NoSuchMechanismException.
If i am totally wrong with my guess, this is no problem , than i have
read this specification and know more about a interessting topic. ;-)
-- Sebastian
Ok. I think i solved it.
But i think it would be good to keep this change here simple and remove
NoSuchMechanismException from it. I uploaded a new webrev here without
changes to NoSuchMechanismException:
http://oss-patches.24.eu/openjdk8/RuntimeException/REBASED_ON_8018d541a7b2/
If i saw it right the old webrev was reviewed by Alan,Andrew,Joe and
Mike. If nobody finds new failures, is there someone (maybe one of the
4) that want to sponsor this one?
For the additional comments regarding "weak uses of
RuntimeException-ctors" from Mike i want to create another Patch,
because i think such changes are in another "change-category". Hope to
be back on this soon.
I will start a new thread for NoSuchMechanismException because there are
some testing problems to solve for it.
-- Sebastian
