[
https://issues.apache.org/jira/browse/TIKA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834681#action_12834681
]
Sami Siren commented on TIKA-378:
---------------------------------
Basically my situation is such that I am extending tika with external parsers.
When deploying, initialization of parsers may fail for many reasons, for
example you might have problems with loading native libraries, class not found
etc. Currently you are totally in the dark what it comes to quessing what is
the problem, you only see that your parser is not there. I am basically seeking
a way to tell the user (via logging or something else) that there was problems
initializing the parsers you have configured and here's the cause of the
problems (eg an exception).
> TikaConfig should notify users if it cannot initialize some parser
> ------------------------------------------------------------------
>
> Key: TIKA-378
> URL: https://issues.apache.org/jira/browse/TIKA-378
> Project: Tika
> Issue Type: Bug
> Components: config
> Reporter: Sami Siren
> Fix For: 0.6
>
>
> It would be nice if TikaConfig would somehow signal that it cannot load
> parser classes. Currently it just silently ignores all throwables.
> I would be ok with about any kind of signaling (even just wrapping and
> rethrowing the exception). If we wan't to maintain back compat in
> functionality we could indroduce a new config option into the configuration
> file or a method in TikaConfig class that would enable rethrowing exceptions
> on parser initializations.
> What do others think?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
