Why Are There Two Json Driver Implementations?

1.	Why Are There Two Json Driver Implementations?
Answer» As always, first for HISTORICAL reasons! Main difference is that the JettisonMappedXmlDriver is a THIN wrapper AROUND Jettison in combination with the StaxDriver, while the JsonHierarchicalStreamDriver uses an own more flexible IMPLEMENTATION, but can only be used to generate JSON, deserialization is not implemented. As always, first for historical reasons! Main difference is that the JettisonMappedXmlDriver is a thin wrapper around Jettison in combination with the StaxDriver, while the JsonHierarchicalStreamDriver uses an own more flexible implementation, but can only be used to generate JSON, deserialization is not implemented.

Answer»

As always, first for HISTORICAL reasons! Main difference is that the JettisonMappedXmlDriver is a THIN wrapper AROUND Jettison in combination with the StaxDriver, while the JsonHierarchicalStreamDriver uses an own more flexible IMPLEMENTATION, but can only be used to generate JSON, deserialization is not implemented.

As always, first for historical reasons! Main difference is that the JettisonMappedXmlDriver is a thin wrapper around Jettison in combination with the StaxDriver, while the JsonHierarchicalStreamDriver uses an own more flexible implementation, but can only be used to generate JSON, deserialization is not implemented.

Discussion

No Comment Found

Related InterviewSolutions

Why Is There No Saxreader?
Can Xstream Generate Classes From Xsd?
Is Xstream A Data Binding Tool?
Can The Performance Of Xstream Be Increased?
How Much Memory Does Xstream Consume?
Is Xstream Thread Safe?
How Does Xstream Compare To Jaxb (java Api For Xml Binding)?
How Does Xstream Compare To Java.beans.xmlencoder?
Is Xstream Xxe Vulnerable (cve-2016-3674)?
Why Does Xstream Not Convert An Java.beans.eventhandler?