Details
Closed
Major
Description
As a step towards easier migration, it would be convenient to have a way to specify fields that should be ignored when unmarshalling because they no longer exist in the class. A possible API:
xstream.ignoreField(Address.class, "fieldThatNoLongerExists");
Issue Links
- is related to
-
XSTR-210
Ignore fields and class types
-
Activity
What do you think of Marcos "dirty solution" to solve this issue ? Does it have drawbacks that I should be aware of ?
I think as Philip Gust that xstream should work as ObjetcInputStream, ignoring fields that are missing from the class and Marcos solution seems to do exactly that...
Norbert C.
added a comment - What do you think of Marcos "dirty solution" to solve this issue ? Does it have drawbacks that I should be aware of ?
I think as Philip Gust that xstream should work as ObjetcInputStream, ignoring fields that are missing from the class and Marcos solution seems to do exactly that... Was implemented in 1.1.3: XStream.omitField()
Jörg Schaible
added a comment - Was implemented in 1.1.3: XStream.omitField() Sorry, my fault. This feature is not yet implemented for deserialization.
Jörg Schaible
added a comment - Sorry, my fault. This feature is not yet implemented for deserialization. Patch with unit test only.
Jörg Schaible
added a comment - Patch with unit test only. OmitField will now be respected also at deserialization. So call:
xstream.omitField(DefiningType.class, "didExistOnce");
to omit a field "didExistOnce" that was defined previously in DefiningType.class, but is gone now.
Jörg Schaible
added a comment - OmitField will now be respected also at deserialization. So call:
xstream.omitField(DefiningType.class, "didExistOnce");
to omit a field "didExistOnce" that was defined previously in DefiningType.class, but is gone now. 
This is a very much needed feature. I would like to get some timeline on when this would evlove.
Please update the mailing list with timneline details ont his issue.
Thanks
Ram