[
https://issues.apache.org/jira/browse/TIKA-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241249#comment-13241249
]
Sergey Beryozkin commented on TIKA-593:
---------------------------------------
> CXF implementation looks much heavier than Jersey, look at "mvn
> dependency:tree"
I guess I'd be happy to discuss this issue elsewhere, but since you brought it
up, here is the 2.6.0-SNAPSHOT one:
[INFO] org.apache.cxf:cxf-rt-frontend-jaxrs:jar:2.6.0-SNAPSHOT
[INFO] +-
org.apache.aries.blueprint:org.apache.aries.blueprint.core:jar:0.3.1:provided
[INFO] | +-
org.apache.aries.blueprint:org.apache.aries.blueprint.api:jar:0.3.1:provided
[INFO] | +- org.apache.aries:org.apache.aries.util:jar:0.3:provided
[INFO] | +- org.slf4j:slf4j-api:jar:1.6.2:provided (version managed from
1.5.11)
[INFO] | +-
org.apache.aries.testsupport:org.apache.aries.testsupport.unit:jar:0.3:provided
[INFO] | \- org.apache.aries.proxy:org.apache.aries.proxy.api:jar:0.3:provided
[INFO] +- org.osgi:org.osgi.core:jar:4.2.0:provided
[INFO] +- junit:junit:jar:4.8.2:test
*************
[INFO] +- org.apache.cxf:cxf-api:jar:2.6.0-SNAPSHOT:compile
[INFO] | +- org.codehaus.woodstox:woodstox-core-asl:jar:4.1.2:runtime
[INFO] | | \- org.codehaus.woodstox:stax2-api:jar:3.1.1:runtime
[INFO] | +- org.apache.ws.xmlschema:xmlschema-core:jar:2.0.1:compile
[INFO] | +-
org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.7.1:compile
[INFO] | \- wsdl4j:wsdl4j:jar:1.6.2:compile
[INFO] +- org.apache.cxf:cxf-rt-core:jar:2.6.0-SNAPSHOT:compile
[INFO] | \- com.sun.xml.bind:jaxb-impl:jar:2.1.13:compile
**************
[INFO] +- org.springframework:spring-core:jar:3.0.7.RELEASE:provided
[INFO] | +- org.springframework:spring-asm:jar:3.0.7.RELEASE:provided
[INFO] | \- commons-logging:commons-logging:jar:1.1.1:provided
[INFO] +- org.springframework:spring-context:jar:3.0.7.RELEASE:provided
[INFO] | +- org.springframework:spring-aop:jar:3.0.7.RELEASE:provided
[INFO] | | \- aopalliance:aopalliance:jar:1.0:provided
[INFO] | +- org.springframework:spring-beans:jar:3.0.7.RELEASE:provided
[INFO] | \- org.springframework:spring-expression:jar:3.0.7.RELEASE:provided
*****************
[INFO] +- javax.ws.rs:jsr311-api:jar:1.1.1:compile
[INFO] +- org.apache.cxf:cxf-rt-bindings-xml:jar:2.6.0-SNAPSHOT:compile
[INFO] +- org.apache.cxf:cxf-rt-transports-http:jar:2.6.0-SNAPSHOT:compile
******************
[INFO] +- org.apache.geronimo.specs:geronimo-servlet_3.0_spec:jar:1.0:provided
[INFO] +- org.apache.cxf:cxf-rt-transports-local:jar:2.6.0-SNAPSHOT:test
[INFO] +- org.apache.cxf:cxf-rt-databinding-jaxb:jar:2.6.0-SNAPSHOT:test
[INFO] | \- com.sun.xml.bind:jaxb-xjc:jar:2.1.13:test
[INFO] +- org.apache.cxf:cxf-rt-transports-http-jetty:jar:2.6.0-SNAPSHOT:test
[INFO] | +- org.eclipse.jetty:jetty-server:jar:7.5.4.v20111024:test
[INFO] | | +- org.eclipse.jetty:jetty-continuation:jar:7.5.4.v20111024:test
[INFO] | | \- org.eclipse.jetty:jetty-http:jar:7.5.4.v20111024:test
[INFO] | | \- org.eclipse.jetty:jetty-io:jar:7.5.4.v20111024:test
[INFO] | | \- org.eclipse.jetty:jetty-util:jar:7.5.4.v20111024:test
[INFO] | \- org.eclipse.jetty:jetty-security:jar:7.5.4.v20111024:test
[INFO] +- org.slf4j:slf4j-jdk14:jar:1.6.2:test
[INFO] +- org.easymock:easymock:jar:3.1:test
[INFO] | +- cglib:cglib-nodep:jar:2.2.2:test
[INFO] | \- org.objenesis:objenesis:jar:1.2:test
[INFO] \- org.apache.cxf:cxf-rt-databinding-aegis:jar:2.6.0-SNAPSHOT:test
Note the strong dependencies surrounded by '************', this is all we have.
FYI the wsdl4j dependency is most likely can be excluded - few people have
confirmed it
I agree it is more monolitic in the 2.5.x. We are doing a major split starting
from 2.6
> 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
