Title: Message
It is
actually not too bad. As specified by the SAX documentation, the XML 1.0
recommendation is not too bad at listing what is a fatal, an error and a
possible warning.
On the
warning side, they leave it open to the parser most of the time, meaning that a
detailed inspection
Title: RE: SAX ErrorHandler errors
I did check the SAX documentation and I found it not very specific either, that is why I sent the email in the mailing list :-)
But it helps anyway.
Thanks.
Thomas
-Original Message-
From: David N Bertoni/Cambridge/IBM [mailto:[EMAIL PROTECTED
Hi Thomas,
I would either consult the documentation for SAX, or ask the question on
the Xerces-C dev list. Fatal errors are usually un-recoverable, and are
related to problems with documents that are not well-formed. Errors are
always validation errors. I'm not sure what warnings are, and t
Title: SAX ErrorHandler errors
If I define a SAX ErrorHandler to be used for my XSLT transformation (XSLTTransformer.setErrorHandler), I can trap 3 different kinds of errors: fatal, error and warning.
Is there a documentation somewhere of what is a fatal, error or warning?
A couple of exampl
Hi Emma,
You cannot open single project file, you must only use the workspace
(Xalan.dsw), since that contains the dependencies for all of the projects.
This is how Microsoft Visual Studio works, so you need to understand that.
Create your own project targetting the appropriate executable typ
Title: links still
Dave, thanks for the step-by-step instructions, I thought i was getting somewhere.
I managed to rebuild the complete Xalan workspace, and if I try to just rebuild one of the projects (e.g. XalanTransformer) from within the Xalan workspace, it goes just fine. However, if I
