[
https://issues.apache.org/jira/browse/TIKA-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729593#comment-14729593
]
Tim Allison commented on TIKA-1657:
-----------------------------------
Ah, ok, got it. Thank you. Y, current plan was just the latter. This only
requires generating the xml based on the objects as they exist in the
TikaConfig (with a few added items, mimeRepository path, etc).
To get the first, we'd have to cache the xml nodes that the deserializer
processed? Is the benefit worth the extra code?
The user can see, with some effort admittedly, the same thing in the latter, no?
Perhaps, start with the latter and add the former if needed?
What's your take of the hierarchical handling in the attached?
> 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
>
> Attachments: TIKA-1558-blacklist-effective.xml
>
>
> 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)
