--- "Andreas L. Delmelle" <[EMAIL PROTECTED]> wrote: > > Could you be a bit more precise? What kind of error > are you getting when FOP > 'blows up'? >
I think he placed an fo:table *immediately* under the fo:header, and there's no informative user-friendly error in 0.20.5 to tell him that that's not allowed in XSL or FOP [1]. Sans validation exception, FOP continues running with an input it has not been programmed to handle, and eventually "blows up" with any number of run time exceptions--NPE's, ClassCastExceptions, etc.--that would tend to occur under the circumstances. The ValidationExceptions prevent that from happening in the future 1.0--FOP halts with a ValidationException on input streams that it has not been programmed to accept (e.g., fo:table under fo:table-header, fo:root under fo:inline), and gives a clear message of the error in the input. No more vague runtime exception "blowups" that don't give the feedback needed to the user when there are problems with the stylesheet. Glen [1] http://www.w3.org/TR/2001/REC-xsl-20011015/slice6.html#fo_table-header (see Contents) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
