You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2009/06/02 00:49:07 UTC

[jira] Resolved: (TIKA-237) Better distinction between SAXException and TikaException

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

Jukka Zitting resolved TIKA-237.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 0.4

Implemented in revisions 780852 and 780859.

> Better distinction between SAXException and TikaException
> ---------------------------------------------------------
>
>                 Key: TIKA-237
>                 URL: https://issues.apache.org/jira/browse/TIKA-237
>             Project: Tika
>          Issue Type: Improvement
>          Components: parser
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 0.4
>
>
> Like TIKA-198 but for SAXException.
> Some of our Parser implementations use XML parsers that may throw SAXExceptions caused by parse errors or other problems with the input document. Such problems should be reported as TikaExceptions to Parser clients as specified in the Parser.parse() documentation and SAXExceptions should only be thrown when the ContentHandler provided by the client throws them.
> Not making this distinction causes problems like TIKA-236.

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