[
https://issues.apache.org/jira/browse/TIKA-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14251952#comment-14251952
]
Sergey Beryozkin commented on TIKA-1497:
----------------------------------------
Hi, yes, looks nice, though returning Response is marginally more flexible in
cases where extra custom headers need to be set (as opposed to doing it from
ContainerResponseFilter), it has no difference for the runtime whether Metadata
is returned as Response entity or directly; the only minor issue and this a CXF
specific only is that it does not play well with client proxy API, which is not
used with Tika tests...
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)
