Why do not use: http://felix.apache.org/site/apache-felix-http-service.html
On Tue, Feb 8, 2011 at 5:06 PM, Chris A. Mattmann (JIRA) <j...@apache.org>wrote: > > [ > https://issues.apache.org/jira/browse/TIKA-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991997#comment-12991997] > > Chris A. Mattmann commented on TIKA-593: > ---------------------------------------- > > My 2c on this: > > +1 to using JAX RS > > RE: the actual implementation, I used Apache CXF for OODT and it's > basically a jar drop in (or MVN pom.xml update) single dependency. Wink is > still Incubating right? > > > Tika network server > > ------------------- > > > > Key: TIKA-593 > > URL: https://issues.apache.org/jira/browse/TIKA-593 > > Project: Tika > > Issue Type: New Feature > > Components: general > > Reporter: Jukka Zitting > > Assignee: Jukka Zitting > > > > 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. > - > For more information on JIRA, see: http://www.atlassian.com/software/jira > > > -- Best regards, Oleg.
