You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (Jira)" <ji...@apache.org> on 2023/06/12 16:54:00 UTC
[jira] [Resolved] (TIKA-4062) OfflineContentHandler/ContentHandlerDecorator does not provide option for custom error handling
[ https://issues.apache.org/jira/browse/TIKA-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Allison resolved TIKA-4062.
-------------------------------
Fix Version/s: 2.8.1
Resolution: Fixed
Thank you [~ravijha] for the unit test!
> OfflineContentHandler/ContentHandlerDecorator does not provide option for custom error handling
> -----------------------------------------------------------------------------------------------
>
> Key: TIKA-4062
> URL: https://issues.apache.org/jira/browse/TIKA-4062
> Project: Tika
> Issue Type: Bug
> Components: tika-core
> Affects Versions: 2.3.0, 2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.8.0
> Reporter: Ravi Ranjan Jha
> Priority: Critical
> Fix For: 2.8.1
>
>
> OfflineContentHandler/ContentHandlerDecorator does not provide option for custom error handling
> Prior to the change of passing OfflineContentHandler to SAX Parser in XMLReaderUtils.parseSAX, one could pass a custom ContentHandlerDecorator to handle exception or override error/warning etc methods. The same is not possible now because the default impl for handleException in the OfflineContentHandler's parent ContentHandlerDecorator just throws exception as shown below:
>
> protected void handleException(SAXException exception) throws SAXException {
> throw exception;
> }
>
> which could probably be (at minimum)
> public void handleException(SAXException exception) throws SAXException {
> handler.handleException(exception);
> }
>
> This is breaking our app's behavior. Please take it as priority.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)