[ https://issues.apache.org/jira/browse/TIKA-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849697#comment-16849697 ]
Sergey Beryozkin edited comment on TIKA-2882 at 5/28/19 1:39 PM: ----------------------------------------------------------------- I see, I was thinking of the 2.x branch :-) Lets start with the https://github.com/apache/tika/tree/2.x/tika-parser-modules idea in 2.0 master ? was (Author: sergey_beryozkin): I see, I was thinking of the 2.x branch :-) Lets starts with the https://github.com/apache/tika/tree/2.x/tika-parser-modules idea in 2.0 master ? > 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 > 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 (v7.6.3#76005)