[jira] [Updated] (TIKA-2977) Tika should throw an exception if a custom parser specified in tika-config.xml can't be loaded

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Updated] (TIKA-2977) Tika should throw an exception if a custom parser specified in tika-config.xml can't be loaded

Tim Allison (Jira)

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

Tim Allison updated TIKA-2977:
------------------------------
    Description:
If you start tika-server and specify a custom parser class in tika-config _but_ you don't then include that jar on the classpath, tika-server silently fails.  

I initially thought that we should make sure that it respects the service loader problem handler (e.g. <service-loader initializableProblemHandler="throw"/>), but this isn't service loading.  If a user specifies a parser that can't be loaded, we should throw an exception.  WDYT?

This also affects tika-app in regular and batch mode.

  was:
If you start tika-server and specify a custom parser class in tika-config _but_ you don't then include that jar on the classpath, tika-server silently fails.  

I initially thought that we should make sure that it respects the service loader problem handler (e.g. <service-loader initializableProblemHandler="throw"/>), but this isn't service loading.  If a user specifies a parser that can't be loaded, we should throw an exception.  WDYY?

This also affects tika-app in regular and batch mode.


> Tika should throw an exception if a custom parser specified in tika-config.xml can't be loaded
> ----------------------------------------------------------------------------------------------
>
>                 Key: TIKA-2977
>                 URL: https://issues.apache.org/jira/browse/TIKA-2977
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Tim Allison
>            Assignee: Tim Allison
>            Priority: Major
>
> If you start tika-server and specify a custom parser class in tika-config _but_ you don't then include that jar on the classpath, tika-server silently fails.  
> I initially thought that we should make sure that it respects the service loader problem handler (e.g. <service-loader initializableProblemHandler="throw"/>), but this isn't service loading.  If a user specifies a parser that can't be loaded, we should throw an exception.  WDYT?
> This also affects tika-app in regular and batch mode.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)