[xsd-users] Hybrid between XSD and XSD/e - parsing
serialisation approach from XSD/e, but feature set and interface of
boris at codesynthesis.com
Thu Jun 16 05:17:44 EDT 2011
Vladimir.Michl at barclayscapital.com <Vladimir.Michl at barclayscapital.com> writes:
> What makes XSD slow is that transformation to DOM and then to C++ objects.
> XSD/e on the other side does not have all the features I would require.
> Is there any way to pick best of both from XSD and XSD/e? E.g. The
> parsing/serialisation approach from XSD/e, but feature set and
> interface from XSD?
No, unfortunately there is no easy way combine the two.
C++/Hybrid in XSD/e is pretty similar conceptually to C++/Tree in XSD,
especially if C++ exceptions and STL are enabled in XSD/e. What are
the specific features of XSD that are missing in XSD/e and that you
Also, you may want to consider using the binary representation of
the object model. For example, you can use it internally in your
application and export to XML only if/when needed for compatibility
with third party systems. Another alternative would be to have a
"fat" format where both the binary and XML representations are present.
Binary parsing/serialization is about an order of magnitude faster
than XML parsing/serialization. For more information see section
5.2, "Binary Serialization" in the C++/Tree Mapping User Manual:
More information about the xsd-users