[
https://issues.apache.org/jira/browse/TIKA-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Burch resolved TIKA-1653.
------------------------------
Resolution: Fixed
Fix Version/s: 1.10
This was caused by {{node.getElementsByTagName("parser")}} checking at all
depths, which wasn't what we needed. Fixed in r1684199 by using a non-recursing
{{getChildNodes()}} call instead
> Tika config xml shouldn't read nested parser definitions as top level
> ---------------------------------------------------------------------
>
> Key: TIKA-1653
> URL: https://issues.apache.org/jira/browse/TIKA-1653
> Project: Tika
> Issue Type: Bug
> Components: config
> Affects Versions: 1.9
> Reporter: Nick Burch
> Fix For: 1.10
>
>
> Spotted while looking at TIKA-1642, if you have some Tika config xml like:
> {code}
> <properties>
> <parsers>
> <parser class="org.apache.tika.parser.ctakes.CTAKESParser">
> <parser class="org.apache.tika.parser.DefaultParser"/>
> </parser>
> </parsers>
> </properties>
> {code}
> Then because of the way that TikaConfig is fetching the elements, it will
> process the DefaultParser once as a child of CTakes, then a second time at
> the top level
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
