[ https://issues.apache.org/jira/browse/TIKA-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16909117#comment-16909117 ]
Sergey Beryozkin commented on TIKA-2882: ---------------------------------------- OK, I've assigned to myself. Well, now that I'll have to do it, I have to say, my priority is to prepare to the Apache Con EU Tika talk well, but I'll give a try (and copy Bob's work from the 2.x branch :-) ) asap. Thanks > 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 (v7.6.14#76016)