[
https://issues.apache.org/jira/browse/TIKA-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476914#comment-13476914
]
Sergey Beryozkin commented on TIKA-894:
---------------------------------------
The following fragment may help:
http://cxf.apache.org/docs/jaxrs-services-configuration.html#JAXRSServicesConfiguration-ConfiguringJAXRSservicesincontainerwithoutSpring
I guess the simplest option is to use
org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet, with
jaxrs.serviceClasses pointing to Tika class, and jaxrs.providers - to Tika
JAX-RS providers
> Add webapp mode for Tika Server, simplifies deployment
> ------------------------------------------------------
>
> Key: TIKA-894
> URL: https://issues.apache.org/jira/browse/TIKA-894
> Project: Tika
> Issue Type: Improvement
> Components: packaging
> Affects Versions: 1.1, 1.2
> Reporter: Chris Wilson
> Labels: maven, newbie, patch
> Attachments: tika-server-webapp.patch
>
>
> For use in production services, Tika Server should really be deployed as a
> WAR file, under a reliable servlet container that knows how to run as a
> system service, for example Tomcat or JBoss.
> This is especially important on Windows, where I wasted an entire day trying
> to make TikaServerCli run as some kind of a service.
> Maven makes building a webapp pretty trivial. With the attached patch
> applied, "mvn war:war" should work. It seems to run fine in Tomcat, which
> makes Windows deployment much simpler. Just install Tomcat and drop the WAR
> file into tomcat's webapps directory and you're away.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
