You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Sergey Beryozkin (Jira)" <ji...@apache.org> on 2019/09/13 11:31:00 UTC
[jira] [Commented] (TIKA-2882) Parsers should not include HTTP
client code
[ https://issues.apache.org/jira/browse/TIKA-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16929130#comment-16929130 ]
Sergey Beryozkin commented on TIKA-2882:
----------------------------------------
I'll create a dedicated issue so that I can link from it from the other sources, etc
> Parsers should not include HTTP client code
> -------------------------------------------
>
> Key: TIKA-2882
> URL: https://issues.apache.org/jira/browse/TIKA-2882
> Project: Tika
> Issue Type: Improvement
> Components: parser
> Affects Versions: 1.21
> Reporter: Jonathan Essex
> Assignee: Sergey Beryozkin
> Priority: Major
>
> Folks, does it really make sense for a parser to have a REST client built in?
> The GROBID and NLTKNERecogniser parsers use the apache CXF client directly.
>
> Since I don't use CXF and my entire app is built on a different JAX-RS stack this just dropped me straight into dependency hell.
> Surely it would make more sense to keep the parsers... well, parsers... and build support for delegating parsing to other services into some higher level in the stack (such as the server, where the CXF dependency is more benign).
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)