Forums » Help »
Problem with ReceivingContentHandler in 8.7.3
Added by Anonymous over 18 years ago
Legacy ID: #3846292
Legacy Poster: Marc Moskowitz (mmoskowi)
I'm having a problem parsing data in Saxon 8.7.3. The exception I'm getting is:
Exception in thread "main" java.lang.NullPointerException at
net.sf.saxon.event.ReceivingContentHandler.getNameCode(ReceivingContentHandler.java:299)
at
net.sf.saxon.event.ReceivingContentHandler.startElement(ReceivingContentHandler.java:234)
at org.gjt.xpp.sax2.Driver.parseSubTree(Driver.java:362) at
org.gjt.xpp.sax2.Driver.parse(Driver.java:310) at
net.sf.saxon.event.Sender.sendSAXSource(Sender.java:270) at
net.sf.saxon.event.Sender.send(Sender.java:144) at
net.sf.saxon.event.Sender.send(Sender.java:46) at
net.sf.saxon.PreparedStylesheet.loadStylesheetModule(PreparedStylesheet.java:201) at
net.sf.saxon.PreparedStylesheet.prepare(PreparedStylesheet.java:126) at
net.sf.saxon.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:135) at
com.ifactory.sageeref.scripts.TransformElement.main(TransformElement.java:42) If I
remove all child elements and the version attribute from xsl:stylesheet, newTemplates()
succeeds but the same error happens at transform(). Where is ReceivingContentHandler? I
can't find it in the CVS repository.
Legacy ID: #3846324
Legacy Poster: Michael Kay (mhkay)
It looks as if the "parser" (org.gjt.xpp.sax2.Driver.parseSubTree)
has passed the Saxon ContentHandler a null URI on the call to startElement. The
"null" namespace should be represented by a zero-length string. You
can find the Saxon source code by going to http://saxon.sf.net/ and following the link
labelled Download documentation, source, and samples (8.9 Mbytes) The CVS repository is
completely out of date.
Legacy ID: #3847576
Legacy Poster: Marc Moskowitz (mmoskowi)
Thanks! The problem turned out to be that Maven had installed a new parser. Setting
the XMLParserFactory property back to Xerces' parser fixed it.
Please register to reply
.