[
https://issues.apache.org/jira/browse/TIKA-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14717320#comment-14717320
]
Chris A. Mattmann commented on TIKA-1716:
-----------------------------------------
fantastic idea. I'm going to implement the fix you suggest above, Tim. My
preference is for @PathParam.
> Tika Server's recursive JSON output from /rmeta different than tika-app -J
> output
> ---------------------------------------------------------------------------------
>
> Key: TIKA-1716
> URL: https://issues.apache.org/jira/browse/TIKA-1716
> Project: Tika
> Issue Type: Bug
> Components: cli, server
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Fix For: 1.11
>
>
> Over in Tika Python, we've received a request for exposing the XHTML output
> that Tika provides. I noticed that in
> [TikaJAXRS|http://wiki.apache.org/tika/TikaJAXRS] that the JSON output from
> /rmeta which Tika Python uses is different from tika-app's -J command. For
> example, see
> [GrobidJournalParser|http://wiki.apache.org/tika/GrobidJournalParser]. I'm
> not sure they should be different. Maybe they should. But it would be nice to
> at least provide maybe X:TIKA:XHTMLContent or something like that in /rmeta
> the same way that Tika-app -J provides.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
