XInclude exceptions - how to mirror Xerces J functionality into Xerces C++? 2007-02-03 - By Simon Rowland
Hi there,
I'm writing an XInclude module for the Xerces C++ parser. Currently I am
writing a DOMDocument -> DOMDocument transformer. Next I will write a
SAX filter to do it live in the parse.
I have a quick question about the Xerces-J implementation and it's
Exceptions. Basically I want to propagate XInclude error messages out of
my module into the client application.
My current thinking is to create a sublcass of XMLException, as many
other Xerces C++ internal errors do (e.g. PlatformUtils etc). This is
also the closest thing I can spot to a similar mechanism to the Xerces J
XInclude code, which uses a XMLParseException which is a sublcass of the
generic XNIException.
My understanding of the spec is that it doesn't specify what we use, as
long as we stop doing the XInclude when we encounter a fatal error.
So any advice from those that have been down the XInclude investgiation
route already? Anything gratefully received!
Many thanks in advance, Simon Rowland.
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@(protected)
For additional commands, e-mail: j-dev-help@(protected)
|
|
