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

Sergey Beryozkin commented on TIKA-593:
---------------------------------------

> I do not completely understand your discussion about 415, but the test failed 
> because TikaExceptionMapper was not added to providers list.

What do you not understand ?
FYI I do not understand how having TikaExceptionMapper registered can result in 
415 being returned, I'm looking at it and seeing no traces of 415, can you 
clarify please ?

> (by the way, maybe CXF supports classpath scanning like Jersey?)

No it does not yet. It was a very specific decision - IMHO the random class 
scanning is impractical in many cases and causes more troubles than it's worth 
and if of little use when the custom providers have to be configured in the 
per-endpoint specific way as in case with most interesting applications. 
However I do accept that for simple mappers it can make sense, though I'm not 
sure what is simpler, restricting the packages to scan or just go and register 
required providers :-), I prefer the latter, but please see#

https://issues.apache.org/jira/browse/CXF-4199

In CXF 2.6.0 FIQL search extensions got moved to the new module, so it is time 
to optionally support it



                
> 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