Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 1.4.3
-
Fix Version/s: None
-
Component/s: Compatibility
-
Labels:None
-
JDK version and platform:Sun/Oracle "1.6.0_31" for Windows
Description
I have XML files that were created using XStream 1.3.1. I can read them fine with version 1.4.2. With version 1.4.3, I get an error. The full stacktrace is an attachment.
com.thoughtworks.xstream.converters.ConversionException: null : null
---- Debugging information ----
cause-exception : java.lang.RuntimeException
cause-message : null
class : java.util.concurrent.ConcurrentHashMap
required-type : java.util.concurrent.ConcurrentHashMap
converter-type : com.thoughtworks.xstream.converters.collections.MapConverter
path : /java.util.concurrent.ConcurrentHashMap/unserializable-parents
line number : 2
version : null
-------------------------------
at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79)
at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(Abstract
Activity
Hi Scott,
the ConcurrentHashMap was handled in previous XStream version by the reflection-based converters. However, since those converters expose implementation details in the XML, the format was not compatible between JDK versions and JDKs of different vendors. Therefore XStream delivers now since version 1.4.3 a specialized converter for this type to prevent such incompatibilities (see XSTR-608).
Simply use two different XStream instances, if you have to read XML written in the old format and register the SerializationConverter again for unmarshalling the ConcurrentHashMap.
Jörg Schaible
added a comment - Hi Scott,
the ConcurrentHashMap was handled in previous XStream version by the reflection-based converters. However, since those converters expose implementation details in the XML, the format was not compatible between JDK versions and JDKs of different vendors. Therefore XStream delivers now since version 1.4.3 a specialized converter for this type to prevent such incompatibilities (see XSTR-608 ).
Simply use two different XStream instances, if you have to read XML written in the old format and register the SerializationConverter again for unmarshalling the ConcurrentHashMap. 
full stack trace