|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
To unsubscribe from this list please visit:
Thank you for your explanations. I run the following adaptation of the example:
XStream xstream = new XStream(new DomDriver());
{List.class, ArrayList.class}Class<?>[] origin =
;
String xml = xstream.toXML(origin);
System.out.println(xml);
Class<?>[] serialized = (Class[]) xstream.fromXML(xml);
System.out.println(serialized[0]);
System.out.println(serialized[1]);
With XStream 1.4.4, the output is the following:
<java-class-array>
<java-class>java.util.List</java-class>
<java-class>java.util.ArrayList</java-class>
</java-class-array>
interface java.util.List
class java.util.ArrayList
When I perform the code changes that are proposed
in http://jira.codehaus.org/browse/XSTR-731, the output is the following:
<java-class-array>
<java-class>list</java-class>
<java-class>java.util.ArrayList</java-class>
</java-class-array>
interface java.util.List
class java.util.ArrayList
That would be O.K. for me.
I use XStream to serialize objects in an installation that is obfuscated by ProGuard. Deserialization takes place in the non-obfuscated counterpart, XStream aliases being filled with the inverse of the obfuscation mapping. The obfuscation mapping guarantees uniqueness and correct handling of primitive types. Everything works fine except the handling of Java class names as mentioned here.