[
https://issues.apache.org/jira/browse/TIKA-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222202#comment-15222202
]
Nick C commented on TIKA-1914:
------------------------------
This error happens when using saxon instead of xalan. Xalan doesn't error even
though startDocument is never called. After adding the call to startDocument
everything works perfectly with saxon.
java.lang.NullPointerException: null
at
net.sf.saxon.event.ReceivingContentHandler.startElement(ReceivingContentHandler.java:279)
at
org.apache.tika.sax.ContentHandlerDecorator.startElement(ContentHandlerDecorator.java:126)
at
org.apache.tika.sax.SafeContentHandler.startElement(SafeContentHandler.java:264)
at
org.apache.tika.sax.XHTMLContentHandler.lazyStartHead(XHTMLContentHandler.java:140)
at
org.apache.tika.sax.XHTMLContentHandler.lazyEndHead(XHTMLContentHandler.java:158)
at
org.apache.tika.sax.XHTMLContentHandler.endDocument(XHTMLContentHandler.java:218)
at
org.apache.tika.parser.executable.ExecutableParser.parse(ExecutableParser.java:82)
> ExecutableParser doesn't call start document
> --------------------------------------------
>
> Key: TIKA-1914
> URL: https://issues.apache.org/jira/browse/TIKA-1914
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 1.12
> Reporter: Nick C
> Priority: Trivial
> Labels: patch
> Fix For: 1.13
>
>
> The ExecutableParser doesn't call start document which causes errors when
> producing XHTML
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
