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 2004/11/11 21:50:06 UTC
DO NOT REPLY [Bug 32193] New: -
NullPointerException when using non-Apache XML parser (Xerces) and/or JXTransformer
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32193>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=32193
NullPointerException when using non-Apache XML parser (Xerces) and/or JXTransformer
Summary: NullPointerException when using non-Apache XML parser
(Xerces) and/or JXTransformer
Product: Fop
Version: 0.20.5
Platform: Other
OS/Version: Linux
Status: NEW
Severity: Critical
Priority: Other
Component: general
AssignedTo: fop-dev@xml.apache.org
ReportedBy: adams@cis.gvsu.edu
On my cite we had an XML parser created by Oracle
(oracle.xml.parser.v2.SAXParser) installed in the system, so FOP was picking it
up and using it before it found Xerces. Same for the JXTransformer class in
oracle.xml.jaxp.JXTransformer. This created a NullPointerException in
JXTransformer.reportXSLException().
My kludge solution was to modify fop.sh and to include both xercesImpl.jar and
xalan.jar in -Xbootclasspath/p: (so they are searched before ANY other JARs).
This eliminated the NullPointerException and everything worked perfectly.
In this bugzilla form I listed this under with OS Linux, but I suspect it would
produce the same effects on any other system where Xerces and Xalan aren't found
first.