[
https://issues.apache.org/jira/browse/TIKA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved TIKA-378.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.7
Assignee: Jukka Zitting
After thinking about this more I decided to remove (see revision 911457) the
empty catch of Throwables introduced for TIKA-217. Now the configuration parser
will throw TikaExceptions whenever it encounters configuration errors.
As mentioned, the main cause for potential exceptions so far has been an
incomplete classpath caused by a deployment choosing (quite correctly) not to
include parser libraries for formats that aren't needed. To avoid such errors I
modified the parser classes in tika-parsers to be loadable even when the
underlying parser library is not available. After this change any exceptions
from TikaConfig are far more likely to be caused by real configuration problems.
> 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
> Affects Versions: 0.6
> Reporter: Sami Siren
> Assignee: Jukka Zitting
> Fix For: 0.7
>
>
> 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.
