[
https://issues.apache.org/jira/browse/ACE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631629#comment-13631629
]
Bram de Kruijff commented on ACE-317:
-------------------------------------
Proposed solution icm ACE-316:
To "make it more REST-full" - The required unique filename path is replace by
an optional filename parameter, relevant only for non-bundles. ACE-316 changed
the store layout thath is now under control of the OBR and not dependent on the
filename provided by the client. A create is a POST to the endpoint and, if the
resource gets stored succesfull, a HTTP response '201 - Created' is returned
with a location header specifying where the resource URI. Subsequent GET/DELETE
operations must then operate on the location URI.
To "detect duplicate bundles more gracefully" - We could simply change from
throwing a CONFLICT to allowing overwrites. If a client wants to preemtively
check wither a specific bundle exists I guess it should check the
repository.xml.
To "support to (re)name bundles" - ACE-316 changes the store location to be
based on symbolicname/version. For bundles these are taken from the manifest
and for other resources the filename can take the form
<symbolicname>-<version>.<extension>. This and the previously mentioned
overwrite support would probably be good enough?
> Improve the REST API for the OBR
> --------------------------------
>
> Key: ACE-317
> URL: https://issues.apache.org/jira/browse/ACE-317
> Project: ACE
> Issue Type: Question
> Components: OBR
> Reporter: Marcel Offermans
> Assignee: Bram de Kruijff
>
> Make it more REST compliant (plain old CRUD).
> Detect duplicate bundle uploads and handle them more gracefully.
> Add support to name or rename bundles so you don't have to make filenames
> unique "by hand".
--
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
