[ 
https://issues.apache.org/jira/browse/TIKA-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14362077#comment-14362077
 ] 

Hudson commented on TIKA-1117:
------------------------------

SUCCESS: Integrated in tika-trunk-jdk1.7 #551 (See 
[https://builds.apache.org/job/tika-trunk-jdk1.7/551/])
TIKA-1117. Don't let iWorkPackageParser close the given InputStream. 
(tpalsulich: http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1666756)
* 
/tika/trunk/tika-parsers/src/main/java/org/apache/tika/parser/iwork/IWorkPackageParser.java
* 
/tika/trunk/tika-parsers/src/test/java/org/apache/tika/parser/iwork/IWorkParserTest.java


> IWorkPackageParser should not close the InputStream
> ---------------------------------------------------
>
>                 Key: TIKA-1117
>                 URL: https://issues.apache.org/jira/browse/TIKA-1117
>             Project: Tika
>          Issue Type: Bug
>          Components: parser
>    Affects Versions: 1.3
>            Reporter: Andrew Jackson
>            Assignee: Tyler Palsulich
>            Priority: Minor
>
> I am using the Tika parser framework embedded in another application, i.e. I 
> am controlling the output InputStream which is then wrapped as a 
> TikaInputStream and parsed. Under these circumstances, I run into problems 
> due to the IWorkPackageParser closing the InputStream. See 
> org.apache.tika.parser.iwork.IWorkPackageParser.parse(IWorkPackageParser.java:219)
> I can avoid this by wrapping my stream in a CloseShieldInputStream, but I 
> suspect this may cause problems more widely. I believe that any Tika Parser 
> implementation should not close the InputStream it is passed, and therefore 
> the .close() call in the IWorkPackageParser should be removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to