[
https://issues.apache.org/jira/browse/TIKA-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253576#comment-14253576
]
Hudson commented on TIKA-1499:
------------------------------
SUCCESS: Integrated in tika-trunk-jdk1.6 #359 (See
[https://builds.apache.org/job/tika-trunk-jdk1.6/359/])
TIKA-1499: fold MetadataEP in tika-server into MetadataResource (tallison:
http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1646779)
* /tika/trunk/CHANGES.txt
* /tika/trunk/tika-server/src/main/java/org/apache/tika/server/MetadataEP.java
*
/tika/trunk/tika-server/src/main/java/org/apache/tika/server/MetadataResource.java
*
/tika/trunk/tika-server/src/main/java/org/apache/tika/server/TextMessageBodyWriter.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/MetadataEPTest.java
*
/tika/trunk/tika-server/src/test/java/org/apache/tika/server/MetadataResourceTest.java
> Let's fold MetadataEP's capabilities into MetadataResource in tika-server
> -------------------------------------------------------------------------
>
> Key: TIKA-1499
> URL: https://issues.apache.org/jira/browse/TIKA-1499
> Project: Tika
> Issue Type: Improvement
> Reporter: Tim Allison
> Priority: Minor
>
> MetadataEP ("/metadata") has three capabilities:
> 1) JSON view of metadata
> 2) String value for a user requested metadata field
> 3) A reduced metadata object that only includes the values of a
> user-requested field
> Given that don't seem to have loaded MetadataEP into tika-server cli, I don't
> think that functionality worked. I could be very wrong, though, about its
> use! Please let me know.
> MetadataResource ("/meta") now handles 1), and I propose folding 2) and 3)
> into MetadataResource and deleting MetadataEP.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
