[
https://issues.apache.org/jira/browse/TIKA-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14034032#comment-14034032
]
Hudson commented on TIKA-1341:
------------------------------
SUCCESS: Integrated in tika-trunk-jdk1.7 #53 (See
[https://builds.apache.org/job/tika-trunk-jdk1.7/53/])
TIKA-1341: fix double endDocument in PDFParser (tallison:
http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1603208)
*
/tika/trunk/tika-parsers/src/main/java/org/apache/tika/parser/pdf/PDFParser.java
*
/tika/trunk/tika-parsers/src/test/java/org/apache/tika/parser/pdf/PDFParserTest.java
> double invocation of handler.endDocument() in PDFParser
> -------------------------------------------------------
>
> Key: TIKA-1341
> URL: https://issues.apache.org/jira/browse/TIKA-1341
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 1.5, 1.6
> Environment: suse linux 64bit, oracle java 7
> Reporter: Christian Reuschling
> Assignee: Tim Allison
> Priority: Critical
> Labels: easyfix
> Fix For: 1.6
>
> Original Estimate: 10m
> Remaining Estimate: 10m
>
> I currently migrate to Tika 1.5, and fall into this behaviour, which leads to
> double entries in my database for one pdf file as I work directly with the
> handler.
> Here are the two calls:
> First call is in PDF2HTML, line 197: handler.endDocument();
> this is part of the PDF2XHTML.process(pdfDocument, handler, context,
> metadata, localConfig);
> invocation from PDFParser, line 143.
> The second call is then directly in PDFParser, line 151:
> handler.endDocument();
> Must stay at Tika 1.4 for now - still thanks for good work!
--
This message was sent by Atlassian JIRA
(v6.2#6252)
