DO NOT REPLY [Bug 6539] New: - Poor error recovery from invalid FO; wrong exit status

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6539>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6539

Poor error recovery from invalid FO; wrong exit status

           Summary: Poor error recovery from invalid FO; wrong exit status
           Product: Fop
           Version: 0.20.3
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: general
        AssignedTo: fop-dev@xml.apache.org
        ReportedBy: jesse.glick@netbeans.com


Run the 'pdf1' target of the Ant build script in the attached example.
Or run XSL and FOP manually. Tested with docbook-xsl 1.48 and Apache
FOP 0.20.3rc. Log file included as log1.txt.

The FO here is incorrect (stylesheet error): there is a <fo:block> as
a direct child of <fo:root>. FOP does not recover from this condition
with a helpful error message, it just throws an NPE which does not
make it easy to figure out what is wrong.

Furthermore the Java process exits with code 0 despite the fact that a
fatal exception was thrown and no readable PDF was generated. It
should exit with code 1. That would e.g. cause the Ant task <java> to
throw a build exception rather than report success.

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org