[
https://issues.apache.org/jira/browse/TIKA-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176596#comment-13176596
]
Jerome Lacoste commented on TIKA-830:
-------------------------------------
>From a desing PoV I find it strange that a special parser isn't supported. In
>order to write integration tests for either fork parsing or non fork parsing I
>have to duplicate a big part of the Tika class.
Another fix I had in mind was to modify Tika#parseToString() to do something
like
{code}
context.set(Parser.class, parser.getUnderlyingParser();
{code}
with parser.getUnderlyingParser() returning this in AbstractParser, but
overriden to return the underlying parser in ForkParser.
Does that make more sense than the ForkParser modifying the ParseContext ?
> Tika.parseToString() causes ForkParser to try to serialize itself
> -----------------------------------------------------------------
>
> Key: TIKA-830
> URL: https://issues.apache.org/jira/browse/TIKA-830
> Project: Tika
> Issue Type: Bug
> Affects Versions: 1.0
> Reporter: Jerome Lacoste
> Priority: Blocker
> Attachments:
> 0005-TIKA-830-Tike.parseToString-caused-ForkParser-to-try.patch,
> 0006-TIKA-830-refactor-tests-for-clarity.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
