Hi David,
David Kelvin <[EMAIL PROTECTED]> writes:
> I have just looked at the Codesynthesis approach ("perfect parser")
> and I am not sure I can easliy (read: quickly) use it as I will have
> a lot of code to add to check my bespoke data types etc. Note: this
> is only after a very very quick glance and is not meant to detract
> from the products or the approach. Given that we already have fully
> working code using the SAX interface of MSXML using schema validation
> of the XML files, I believe that it will be quicker/easier to just
> convert this to the Xerces SAX2 interface. I think most of the
> MSXML SAX handler code can be 'lifted' and 'placed' into the
> Xerces SAX2 handler routines.
If you already have your application logic implemented against the
SAX2 interface then it will definitely be easier to swap the SAX2
implementations than to move to a new API.
The advantage of the perfect parser approach is that the XML
Schema validation, specific to your schemas, will be performed
by the generated code so that your application does not need
to depend on a general-purpose validating XML parser like MSXML
or Xerces-C++.
Boris
--
Boris Kolpackov, Code Synthesis Tools http://codesynthesis.com/~boris/blog
Open source XML data binding for C++: http://codesynthesis.com/products/xsd
Mobile/embedded validating XML parsing: http://codesynthesis.com/products/xsde
