c# - Complex schema validation issues - Stack Overflow
All XML data binding products can round-trip elements, attributes, and text, as well as the hierarchical relationships among them. However, most XML data binding products cannot preserve anything else, such as comments or entity references. (A notable exception to this is , which is designed to round-trip XML documents.) As a general rule, this is not a serious problem, since applications that use XML data binding tend to be interested only in the data in an XML document, rather the way in which it is represented.
Complex schema validation issues
by Mette Hedin
A comparison of Breeze XML Binder, Castor, the JAXB Reference Implementation, and XGen. The first part of the article compares how well the products support XML Schemas and whether the resulting code (a) compiles and (b) can round-trip documents. The second part compares some features of the products and is clearly biased towards XGen (the author was the technical lead of XGen). It is nonetheless useful in describing some of the challenges in designing XML data binding tools.
by Dennis M. Sosnoski
An excellent four-part comparison of JAXB, Castor, JBind, Quick, Zeus, and JiBX. Part 1 discusses the pros and cons of each product (except JiBX) and shows the code generated by each for a particular schema. Part 2 compares performance and memory usage. Part 3 discusses the architecture of JiBX, but also discusses design choices used by the other products. Part 4 discusses JiBX in greater detail. If you understand XML data binding and are trying to decide which product to use, this is a great place to start.
Voice Extensible Markup Language (VoiceXML) Version …
Document fragment limitations. It appears that no XML data binding products can operate on document fragments. That is, they cannot extract data from one or more fragments of an XML document, expose that data using schema-specific objects, and re-write those fragments to the document, leaving the rest of the document unchanged. This is a real problem in workflow scenarios, where a series of applications works on a document, each modifying part of the document and passing it to the next application. As a workaround, applications must extract and re-insert fragments themselves.