Matt Hogstrom wrote:
Not being totally familiar with all the nuances in G WRT to
serialization my comments should be taken with a grain of salt. From my
perspetive there are two major problems with serialized data. One, its
very fragile
Yes.
and two you can't change it if you need to. One could
argue users shouldn't be changing it but in extreme circumstances it is
unavoidable.
I'd vote for the move to XML (ouch, did I say that?)
Matt
My inclination as well. I've been scratching my head trying to understand 'why serialization?' rather than
nice, flat, intuitive text files. There may be a very good answer I just don't what it is.
Jeremy Boynes wrote:
Sachin's problem is not related to configuration persistence but to
the serialization of classes between plugin and server when using JMX
remoting over RMI.
The upshot of it all is unless we are going to ditch all use of
serialization and replace it with XML then we need to exercise the
necessary discipline and version the classes involved.
--
Jeremy
