Re: Exception hierarchy.

2004-10-27 Thread Finn Bock
[Andreas] It seems more about not throwing SAXParseExceptions, but catching them and throwing a FOPException instead. Isn't that the issue? That a 'missingChildElementError' is actually not a SAXParseException... because it has nothing to do with SAX in itself [Glen] SAXParseExceptions would

RE: Exception hierarchy.

2004-10-27 Thread Andreas L. Delmelle
-Original Message- From: Glen Mazza [mailto:[EMAIL PROTECTED] snip / As the definition of its parent SAXException[1] states, This class can contain basic error or warning information from either the XML parser *or the application* So it can be used within FOP. True, but I still

Re: Exception hierarchy.

2004-10-27 Thread J.Pietschmann
Finn Bock wrote: ValidateException is the right choice of exception when the FO file doesn't follow the content model. Nitpick: s/FO file/FO processor input document/ J.Pietschmann

Re: page-number-citation problem

2004-10-27 Thread J.Pietschmann
Randy Ouellette wrote: We are having an issue with using the page-number-citation for outputting the page-number for those pages that are inside a page-sequence when the number is restarted (initial-number=1). We are trying to output a page-number in a TOC but cannot get a value. Please provide: -

Re: Exception hierarchy.

2004-10-27 Thread Glen Mazza
Finn, I am more in agreement with your patch. +0 as-is. --- Finn Bock [EMAIL PROTECTED] wrote: [Finn] [Glen] SPE might be considered the XML parsing equivalent of a syntax error that would occur for a code compilation error. Right, errors at the XML level. It *can* be used

RE: Exception hierarchy.

2004-10-27 Thread Glen Mazza
--- Andreas L. Delmelle [EMAIL PROTECTED] wrote: You might want to try searching Xalan source code BTW: I don't think Xalan's actually throwing them anywhere, it merely *uses* them in the sense of 'catch and possibly throw a TransformerException' or define a method with 'throws