The currently used --server mode of the tika-app.jar bundle has a couple issues for use in production, first and foremost the leaking of temporary files that don't get cleaned up by Tika.
There is an alternative server implementation that is supposed to be more robust for production deployments, called TikaJAXRS. This server provides a HTTP interface with a RESTful API.
ftw.tika therefore needs to implement the logic to talk to the JAXRS server via HTTP, and buildouts need to be updated to download and build the new server component.
The currently used
--server
mode of thetika-app.jar
bundle has a couple issues for use in production, first and foremost the leaking of temporary files that don't get cleaned up by Tika.There is an alternative server implementation that is supposed to be more robust for production deployments, called TikaJAXRS. This server provides a HTTP interface with a RESTful API.
ftw.tika
therefore needs to implement the logic to talk to the JAXRS server via HTTP, and buildouts need to be updated to download and build the new server component.