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

Sergey Beryozkin edited comment on TIKA-593 at 3/29/12 3:36 PM:
----------------------------------------------------------------

Max,

> ... That exception mapper was lost after transition from Jersey to CXF, so we 
> had 500-error instead of 415.

Right. The good thing we know the cause and as I indicated we will get to the 
optional class scanning support in CXF.

The funny side to it is that we spent a lot of time with Chris thinking how 
Jersey magically turns away "xxx/xxx" with 415, we thought initially Jersey 
blocked it even before dispatching, but as it happens it was also passing it 
through :-)

Update: Max, sure, we can talk on Jabber, please share your id with me on #cxf 
or post here
                
      was (Author: sergey_beryozkin):
    Max,

> ... That exception mapper was lost after transition from Jersey to CXF, so we 
> had 500-error instead of 415.

Right. The good thing we know the cause and as I indicated we will get to the 
optional class scanning support in CXF.

The funny side to it is that we spent a lot of time with Chris thinking how 
Jersey magically turns away "xxx/xxx" with 415, we thought initially Jersey 
blocked it even before dispatching, but as it happens it was also passing it 
through :-)
                  
> 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

        

Reply via email to