[
https://issues.apache.org/jira/browse/TIKA-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14031662#comment-14031662
]
Hudson commented on TIKA-1336:
------------------------------
SUCCESS: Integrated in tika-trunk-jdk1.6 #45 (See
[https://builds.apache.org/job/tika-trunk-jdk1.6/45/])
- fix for TIKA-1336 This closes #10 (mattmann:
http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1602617)
* /tika/trunk/tika-server/README
*
/tika/trunk/tika-server/src/main/java/org/apache/tika/server/DetectorResource.java
*
/tika/trunk/tika-server/src/main/java/org/apache/tika/server/TikaServerCli.java
*
/tika/trunk/tika-server/src/test/java/org/apache/tika/server/DetectorResourceTest.java
* /tika/trunk/tika-server/src/test/resources/CDEC_WEATHER_2010_03_02
* /tika/trunk/tika-server/src/test/resources/foo.csv
> Provide a Detector JAXRS endpoint
> ---------------------------------
>
> Key: TIKA-1336
> URL: https://issues.apache.org/jira/browse/TIKA-1336
> Project: Tika
> Issue Type: Improvement
> Components: detector, server
> Affects Versions: 1.5
> Reporter: Nick Burch
> Assignee: Chris A. Mattmann
> Fix For: 1.6
>
>
> As identified in TIKA-1335, the Tika Server now has an endpoint which will
> tell you what Detectors are available to it, but not one that will trigger
> detection. That means your only way to do detection is to request the
> metadata, and check the content type, but that isn't always as accurate as an
> explicit detection call (eg if a general parser picks up the file)
> We should therefore add in a new endpoint that just does the detection
--
This message was sent by Atlassian JIRA
(v6.2#6252)
