[Glen]
I'm confused--why is OK to throw SAXExceptions but not its child SAXParseExceptions? With the latter, it just holds locator information necessary to pinpoint the problem for the user. Please elaborate.
The way I see it SAXException is the exception used to communicate across the ContentHandler event methods. And SAXParseException is used to communicate an actual error during parsing of XML. That is what the exception type specify.
And BTW, the patch does not throw any SAXExceptions.
Java gives us a large family of predefined exceptions for use in our coding--I'm leery of proclamations of them being No Good and that each and every Java application must re-invent their own exceptions instead. That just seems sloppy.
But the java exceptions are Very Good. There is just isn't any of them that specifies an error found during XSL:FO validation or found during property evaluation of XSL:FO expressions.
Glen (who wanted to get rid of FOPException and just rely on the Java-defined exceptions)
IMHO reusing SAXParseException is exactly as wrong as reusing f.ex. FileNotFoundException, which is another fine exception, just not suited for use from within FO tree building.
regards, finn
