[
https://issues.apache.org/jira/browse/TIKA-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252239#comment-14252239
]
Sergey Beryozkin commented on TIKA-1497:
----------------------------------------
Hi Tim, sorry for a delay, if you are also fine with it then yes, it would be a
bit more flexible (we won't need to update method signatures in the furture if
the custom headers like etags, etc will need to be added).
MetadataEP, should it be merged into MetadataResource as Chris suggested or
you;d prefer to wait till 2.0 ?
Cheers, Sergey
> tika-server cannot output JSON
> ------------------------------
>
> Key: TIKA-1497
> URL: https://issues.apache.org/jira/browse/TIKA-1497
> Project: Tika
> Issue Type: Improvement
> Components: server
> Reporter: Peter Bowyer
> Attachments: TIKA-1497.patch, TIKA-1497v2.patch
>
>
> I would like the response from
> curl -X PUT -T /path/to/file.pdf http://localhost:9998/meta
> to be JSON and not CSV?.
> I've discovered JSONMessageBodyWriter.java
> (https://github.com/apache/tika/blob/af19f3ea04792cad81b428f1df9f5ebbb2501913/tika-server/src/main/java/org/apache/tika/server/JSONMessageBodyWriter.java)
> so I think the functionality is present, tried adding --header "Accept:
> application/json" to the cURL call, in line with the documentation for
> outputting CSV, but no luck so far.
> According to [~sergey_beryozkin]
> "I see MetadataResource returning StreamingOutput and it has
> @Produces(text/csv) only. As such this MBW has no effect at the moment.
> We can update MetadataResource to return Metadata directly if
> application/json is requested or update MetadataResource to directly convert
> Metadata to JSON in case of JSON being accepted."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
