[
https://issues.apache.org/jira/browse/TIKA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834464#action_12834464
]
Ken Krugler commented on TIKA-378:
----------------------------------
Would it be sufficient to add a method that forces initialization of all known
parsers?
Or is this a runtime situation, where you want an exception thrown when either
an explicit Tika parser can't load the required implementation jar, or the
Autodetect parser hits the same situation?
> 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.
