[xsd-users] xsd exceptions again
Boris Kolpackov
boris at codesynthesis.com
Fri May 21 11:00:36 EDT 2010
Hi Eric,
Eric Niebler <eric at boostpro.com> writes:
> Why don't invalid_utf8_string and invalid_utf16_string inherit from
> ::xsd::cxx::tree::exception? Or anything? Sadly, we only found this
> problem after deploying in the field. I've asked before: is there a
> COMPLETE list of exceptions I need to catch when I call a serialize
> function? The list seems endless, and I can't find it documented
> anywhere.
I have created a FAQ entry #1.3 that hopefully provides a complete
coverage of this topic:
http://wiki.codesynthesis.com/Tree/FAQ
Let me know if you think I missed anything.
> I'd like to make a feature request (again): *all* exceptions that
> propagate out of any xsd function are part of a single documented
> exception hierarchy, preferably rooted at a standard exception.
Yes, this feature is already on the TODO list, along with the
interception and translation of the Xerces-C++ exceptions.
Boris
More information about the xsd-users
mailing list