Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.3
-
Component/s: None
-
Labels:None
Description
The XStream.omitField() method behaves as expected for ReflectionConverter. However, when an object uses custom serialization (writeObject()) and calls ObjectOutputStream.defaultWriteOut(), the fields are not omitted. This is because SerializableConverter does not take into account these fields.
Example of this can be seen here: http://article.gmane.org/gmane.comp.java.xstream.user/1478
Issue Links
- supercedes
-
XSTR-415
Let JavaBeanConverter use bean introspection
-
Activity
A simple test to check if javabean respects the omitted fields
Hinse ter Schuur
added a comment - A simple test to check if javabean respects the omitted fields Modified patch with fixes for inheritance of omitted fields and field aliases
Hinse ter Schuur
added a comment - Modified patch with fixes for inheritance of omitted fields and field aliases The patch for the JavaBeanConverter has been applied.
Jörg Schaible
added a comment - The patch for the JavaBeanConverter has been applied. Alias and omit field is now also respected by the SerializableConverter.
Jörg Schaible
added a comment - Alias and omit field is now also respected by the SerializableConverter. Closing issues before next release.
Jörg Schaible
added a comment - Closing issues before next release. 
It also does not honor the new alias mechanism for fields. Now that we have an AbstractReflectionConverter, we can maybe refactore the code even more to support both issues with one code base.