tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-593) Tika network server
Date Fri, 11 Nov 2011 03:54:51 GMT

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

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

Ingo, I applied your patch to my local copy, but am still seeing test failures:

{noformat}
INFO: Stopping the Grizzly Web Container...
Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 9.341 sec <<< FAILURE!

Results :

Tests in error: 
  testExeDOCX(org.apache.tika.server.UnpackerResourceTest): PUT http://localhost:9998/unpacker
returned a response status of 204 No Content

Tests run: 11, Failures: 0, Errors: 1, Skipped: 0

{noformat}
                
> 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.1
>
>         Attachments: 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

        

Mime
View raw message