[
https://issues.apache.org/jira/browse/TIKA-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175622#comment-13175622
]
Jukka Zitting commented on TIKA-830:
------------------------------------
I'm not sure if we should try to support passing a ForkParser as an argument to
the Tika constructor.
The ForkParser expects the "real" parser instance to be passed in the
ParseContext, which isn't currently supported by the Tika facade.
Instead of adding workarounds like this, I'd rather consider whether we want to
extend the Tika facade to explicitly support forked parsing as a special mode.
Personally I'd rather recommend people who need the ForkParser functionality to
use the class directly instead of through the Tika facade (that's intended to
be just a simple entry point for basic Tika functionality).
> 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
