[
https://issues.apache.org/jira/browse/TIKA-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095371#comment-13095371
]
Jukka Zitting commented on TIKA-701:
------------------------------------
The idea behind that logic is that if the stream we were given is already a
TikaInputStream, then someone higher up in the call chain is already responsible
for properly closing it and thus releasing all associated resources. In that
case
we can simply ignore the given TemporaryResources instance (the dispose() or
close()
call will simply be a no-op with no resources to release), and return the given
stream as-is. Any resources associated with the stream will get released when
the
original creator of the TikaInputStream instance eventually closes the stream.
> Fix problems with TemporaryFiles
> --------------------------------
>
> Key: TIKA-701
> URL: https://issues.apache.org/jira/browse/TIKA-701
> Project: Tika
> Issue Type: Bug
> Affects Versions: 0.9
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Fix For: 1.0
>
>
> As discussed on dev@, there are still some design issues with the
> TemporaryFiles class that we introduced in TIKA-567. They should be solved in
> time for Tika 1.0.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
