[jira] [Commented] (TIKA-2460) Possibility to add custom-mimetypes.xml (and/or also other configuration files) from location outside classpath

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

[jira] [Commented] (TIKA-2460) Possibility to add custom-mimetypes.xml (and/or also other configuration files) from location outside classpath

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/TIKA-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158695#comment-16158695 ]

Nick Burch commented on TIKA-2460:
----------------------------------

I'd tweak the comment to {{System property to set a path to an addition external custom mimetypes XML file to be loaded}}, to make it clear that the name doesn't matter, and that it won't affect the loading of any {{custom-mimetypes.xml}} files already on the classpath

Probably also tweak the next comment addition to {{It will also load custom mimetypes from the system property \{\@link #CUSTOM_MIMES_SYS_PROP\}, if specified}}

Finally, if you give a non-existant path to {{tika.config}} you get a helpful error message {{"Specified Tika configuration not found: " + config}} - should we also add a File exists check + throw a similar specific helpful exception for missing specified mimetype file?

> Possibility to add custom-mimetypes.xml (and/or also other configuration files) from location outside classpath
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: TIKA-2460
>                 URL: https://issues.apache.org/jira/browse/TIKA-2460
>             Project: Tika
>          Issue Type: Improvement
>          Components: mime
>    Affects Versions: 1.11
>            Reporter: Viorica Visan
>            Priority: Minor
>         Attachments: TIKA-2460.patch, TIKA-2460.patch
>
>
> I would like to be able to pass to tika the custom-mimetypes.xml from outside classpath, because it is more flexible.
> Our application is based on eclipse/osgi and it's composed of multiple plugins/bundles.
> One of these plugins contains also the tika library (almost all settings are default)
> We usually provide some configuration, from outside to these plugins.
> And we would like to do the same with tika, because we recently encountered: https://issues.apache.org/jira/browse/TIKA-2443 and had to provide a custom type to workaround a mismatched detection.
> There might be other potential mismatches and it would be good to give this possibility to pass configuration to tika from outside our application. Only that for the osgi setup, on classpath means inside the folder plugin.
> and from our point of view, that is not a good place, because these plugins get replaced at every release, so this patching would have to be maintained all the time.
> This is the reason  why it would be good, if tika itself had this possibility. Thank you.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)