You are viewing a plain text version of this content. The canonical link for it is here.

Posted to fop-dev@xmlgraphics.apache.org by bu...@apache.org on 2003/09/29 14:17:14 UTC

DO NOT REPLY [Bug 23480] New: - [PATCH] NullPointerException when -classpath is empty

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=23480>.
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=23480

[PATCH] NullPointerException when -classpath is empty

           Summary: [PATCH] NullPointerException when -classpath is empty
           Product: Fop
           Version: 0.20.5
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: general
        AssignedTo: fop-dev@xml.apache.org
        ReportedBy: ilatypov@infradead.org


The following error occurs when constructing the instance of Driver
when the all jars are moved into the -Xbootclasspath/p: option.
=======================================================
Converting XSL-FO to PDF...
java.lang.NullPointerException
        at org.apache.fop.apps.Service.providers(Driver.java:597)
        at org.apache.fop.apps.Driver.setupDefaultMappings(Driver.java:318)
        at org.apache.fop.apps.Driver.<init>(Driver.java:222)
        at com.mdldoors.domgenerate.DOMGenerate.convertDOM2PDF(DOMGenerate.java:125)
        at com.mdldoors.domgenerate.DOMGenerate.main(DOMGenerate.java:546)
=======================================================

The the class loader instance cl is null in this case.  The attached patch
works around this issue.  I am not sure of the consequences of ignoring
the class loader.