[ 
https://issues.apache.org/jira/browse/TIKA-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241259#comment-13241259
 ] 

Chris A. Mattmann commented on TIKA-593:
----------------------------------------

Hey Max:

{quote}
{quote}
    The cool part is that we reduce a bunch of the Maven dependencies with CXF 
and we are eating our own dog food.
{quote}
CXF implementation looks much heavier than Jersey, look at "mvn dependency:tree"
{quote}

I guess here I was talking more about simply only having to rely on *one* Maven 
dependency tag in the tika-server pom.xml for cxf-rt-frontend-jars, rather than 
jersey server + core, and the other dependencies we used to have. If you look 
at the pom.xml, the deps are now reduced. That's what I was thinking (maybe a 
side effect?)

                
> Tika network server
> -------------------
>
>                 Key: TIKA-593
>                 URL: https://issues.apache.org/jira/browse/TIKA-593
>             Project: Tika
>          Issue Type: New Feature
>          Components: general
>    Affects Versions: 0.10
>            Reporter: Jukka Zitting
>            Assignee: Chris A. Mattmann
>             Fix For: 1.2
>
>         Attachments: TIKA-593.Mattmann.032612.patch.2.txt, 
> TIKA-593.Mattmann.032612.patch.txt, TIKA-593.Mattmann.032712.patch.2.txt, 
> TIKA-593.Mattmann.032712.patch.txt, TIKA-593_pom.diff
>
>
> It would be cool to be able to run Tika as a network service that accepts a 
> binary document as input and produces the extracted content (as XHTML, text, 
> or just metadata) as output. A bit like TIKA-169, but without the dependency 
> to a servlet container.
> I'd like to be able to set up and run such a server like this:
>     $ java -jar tika-app.jar --port 1234
> We should also add a NetworkParser class that acts as a local client for such 
> a service. This way a lightweight client could use the full set of Tika 
> parsing functionality even with just the tika-core jar within its classpath.

--
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

        

Reply via email to