tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (TIKA-198) Better distinction between IOException and TikaException
Date Wed, 27 May 2009 18:35:45 GMT

     [ https://issues.apache.org/jira/browse/TIKA-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jukka Zitting resolved TIKA-198.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 0.4

Implemented in revision 778043.

> Better distinction between IOException and TikaException
> --------------------------------------------------------
>
>                 Key: TIKA-198
>                 URL: https://issues.apache.org/jira/browse/TIKA-198
>             Project: Tika
>          Issue Type: Improvement
>          Components: parser
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 0.4
>
>
> As discussed on the mailing list (http://markmail.org/message/qspwa2nqq5fksccs), many
parser libraries throw IOExceptions even for errors that are not caused by problems reading
bytes from the given document input stream. Tika should do a better job of catching such exceptions
and converting them to TikaExceptions to better meet the Parser interface contract.
> In Commons IO I just added a TaggedInputStream class (see IO-192) that is designed for
better handling such cases.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message