[
https://issues.apache.org/jira/browse/TIKA-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14718591#comment-14718591
]
Hudson commented on TIKA-1716:
------------------------------
SUCCESS: Integrated in tika-trunk-jdk1.7 #846 (See
[https://builds.apache.org/job/tika-trunk-jdk1.7/846/])
TIKA-1716 change default /rmeta content handler to xml and allow users to
specify which content handler to use for content (tallison:
http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1698329)
* /tika/trunk/CHANGES.txt
*
/tika/trunk/tika-batch/src/main/java/org/apache/tika/batch/builders/DefaultContentHandlerFactoryBuilder.java
*
/tika/trunk/tika-core/src/main/java/org/apache/tika/sax/BasicContentHandlerFactory.java
*
/tika/trunk/tika-server/src/main/java/org/apache/tika/server/resource/RecursiveMetadataResource.java
*
/tika/trunk/tika-server/src/test/java/org/apache/tika/server/RecursiveMetadataResourceTest.java
> 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: Tim Allison
> 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)
