We should at least keep the deserialization code around forever for backward compatibility. You can select which deserializer to use based on the root element or something, that shouldn't be tough.
-David On Feb 13, 2010, at 8:53 PM, Adrian Crum wrote: > I recently added the XStream library to the project - which enables > serializing/deserializing Java objects to XML or JSON. > > With that addition, the XmlSerializer class is no longer needed. The XStream > library is more sophisticated and extensible than the home-grown code. > > Switching XML serializers introduces a potential compatibility problem with > existing installations - since Java objects are stored in the database in XML > format. I believe I have come up with a strategy that provides a migration > path, and I'm testing some ideas now. > > So, I just wanted to let the community know what I have in mind and see if > there are any comments. > > -Adrian > > > >
