[
https://issues.apache.org/jira/browse/RAVE-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751516#comment-13751516
]
Chris Geer commented on RAVE-1048:
----------------------------------
Rohit, you missed my point. Erin's original point was that you just wanted to
call "save" and not have to care if it's an update or create. My questions was,
if you need different logic in the UI to validate information differently you
would need to care if it was an update or create, therefore you could call a
different method and therefore use PUT.
Maybe I'm being overly picky here but we are using angular on our project as
well now and we've been adding an update method to our resources to handle this
exact case and it hasn't been too cumbersome. In fact, what we've found out is
that we have had to do a lot of additions to the resources over time as a
simple "save" hasn't be sufficient. If no one else agrees with me I will back
off and you can change all the web services to handle POST for updates.
> Have update rest methods accept both put and post requests.
> -----------------------------------------------------------
>
> Key: RAVE-1048
> URL: https://issues.apache.org/jira/browse/RAVE-1048
> Project: Rave
> Issue Type: Sub-task
> Components: rave-core
> Reporter: Erin Noe-Payne
> Fix For: 0.23
>
>
> Angular's $resource service uses post methods to save new or updated
> resources. For simplicity, we should update the rest api endpoints so that
> update methods accept PUT or POST requests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
