XML data binding


XML data binding refers to a means of representing information in an XML document as a business object in computer memory. This allows applications to access the data in the XML from the object rather than using the DOM or SAX to retrieve the data from a direct representation of the XML itself.

Description

An XML data binder accomplishes this by automatically creating a mapping between elements of the XML schema of the document we wish to bind and members of a class to be represented in memory.
When this process is applied to convert an XML document to an object, it is called unmarshalling. The reverse process, to serialize an object as XML, is called marshalling.
Approaches to data binding can be distinguished as follows:
Since XML is inherently sequential and objects are not, XML data binding mappings often have difficulty preserving all the information in an XML document. Specifically, information like comments, XML entity references, and sibling order may fail to be preserved in the object representation created by the binding application. This is not always the case; sufficiently complex data binders are capable of preserving 100% of the information in an XML document.
Similarly, since objects in computer memory are not inherently sequential, and may include links to other objects, XML data binding mappings often have difficulty preserving all the information about an object when it is marshalled to XML.

Alternatives

An alternative approach to automatic data binding relies instead on hand-crafted XPath expressions that extract the data from XML. This approach has a number of benefits. First, the data binding code only needs proximate knowledge of the XML tree structure, which developers can determine by looking at the XML data; XML schemas are no longer mandatory. Furthermore, XPath allows the application to bind the relevant data items and filter out everything else, avoiding the unnecessary processing that would be required to completely unmarshall the entire XML document. The drawback of this approach is the lack of automation in implementing the object model and XPath expressions. Instead the application developers have to create these artifacts manually.

Data binding in general

One of XML data binding's strengths is the ability to un/serialize objects across programs, languages, and platforms. You can dump a time series of structured objects from a datalogger written in C on an embedded processor, bring it across the network to process in Perl and finally visualize in Octave. The structure and the data remain consistent and coherent throughout the journey, and no custom formats or parsing is required. This is not unique to XML. YAML, for example, is emerging as a powerful data binding alternative to XML. JSON is often suitable for lightweight or restricted applications.

XML data binding frameworks

NameProgramming LanguageLicenseFirst releaseLast stable releaseCode generation from XSDCustom mappingNote
Apache Commons BetwixtJava0.8Dormant. Serializes objects to XML without requiring an XML schema definition
Apache XMLBeansJava3.1.0,
CastorJava1.4.1, Earlier versions also supported Java-to-SQL persistence but this has since been forked into a separate project
CodeSynthesis XSDC++ and proprietary4.0.0, with SAX or tree-like mapping into C++ classes
gSOAPC and C++ and proprietary2.8.94, Supports XML schema, WSDL, and SOAP; XML schemas are not required to serialize C/C++ data to XML; custom mapping of XML schema types to C/C++ types via a type mapping file and from C/C++ types to compatible XML schema types by source code annotation
Java Architecture for XML Binding Java?
JiBXJava1.2.6, Maps classes to XML schemas via bytecode manipulation
Java2.7.1,
System.Xml.SerializationC#?Part of the.NET framework, contains XML data binding classes; includes xsd.exe tool to generate classes from XSD schema
xmlbeansxxC++0.9.1, C++ port of Apache XMLBeans
XStreamJava1.4.10, Also capable of serializing to JSON
Java?3.5 beta,