[jira] [Commented] (TIKA-1657) Allow easier XML serialization of TikaConfig

["Tim Allison (JIRA)" <ji...@apache.org>]

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

Tim Allison commented on TIKA-1657:
-----------------------------------

Plan C: abandon the notion of full round-trip-ability and serialize only the "effective" TikaConfig...only serialize those parsers/supported mimes that are included/active.

This will get rid of the need to store both included and excluded mimes and parsers.  We'd still need 1. and 2. from above, but we could get rid of the 3-6.

> Allow easier XML serialization of TikaConfig
> --------------------------------------------
>
>                 Key: TIKA-1657
>                 URL: https://issues.apache.org/jira/browse/TIKA-1657
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Tim Allison
>            Priority: Minor
>             Fix For: 1.11
>
>
> In TIKA-1418, we added an example for how to dump the config file so that users could easily modify it.  I think we should go further and make this an option at the tika-core level with hooks for tika-app and tika-server.  I propose adding a main() to TikaConfig that will print the xml config file that Tika is currently using to stdout.
> I'd like to put this into core so that e.g. Solr's DIH users can get by without having to download tika-app separately.  
> There's every chance that I've not accounted for issues with dynamic loading etc.  Also, I'd be ok with only having this available in tika-app and tika-server if there are good reasons.
> Feedback?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)