[
https://issues.apache.org/jira/browse/TIKA-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361268#comment-14361268
]
Tyler Palsulich commented on TIKA-891:
--------------------------------------
I took a stab at adding the {{@POST}} annotation to each {{@PUT}} resource.
But, it didn't work. Turns out, you cannot support two HTTP request methods for
the same resource. See [this
blog|http://marxsoftware.blogspot.com/2010/02/playing-with-jerseyjax-rs-method.html#post-body-8986464064706467213]
for an experiment. I couldn't seem to find anything in the [official
documentation|http://docs.oracle.com/cd/E19798-01/821-1841/giepu/index.html].
But, the blog and my own experience seem like reason enough.
So, now the real question: Since we can't support {{@PUT}} and {{@POST}}, do we
want to leave everything the way it is, or switch everything to {{@POST}}?
I'm leaning toward leaving the resources the way they are. But, {{@POST}}, as
discussed above, isn't necessarily wrong...
> Use POST in addition to PUT on method calls in tika-server
> ----------------------------------------------------------
>
> Key: TIKA-891
> URL: https://issues.apache.org/jira/browse/TIKA-891
> Project: Tika
> Issue Type: Improvement
> Components: general
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Priority: Trivial
> Labels: newbie
> Fix For: 1.9
>
>
> Per Jukka's email:
> http://s.apache.org/uR
> It would be a better use of REST/HTTP "verbs" to use POST to put content to a
> resource where we don't intend to store that content (which is the
> implication of PUT). Max suggested adding:
> {code}
> @POST
> {code}
> annotations to the methods we are currently exposing using PUT to take care
> of this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
