...
- Get the content of a collection.
- Add a collection
- Delete a given collection
| Note | ||||||
|---|---|---|---|---|---|---|
The following terms explains the meaning of the parameters passed with the below REST URIs
When user adds a collection to the registry, user has to specify the Content-Type of the collection in the request. The Content-Type for the collection is "application/atomcoll+xml". If user specifies a different content-type for the collection, the resource to be added wont be considered as a collection. |
Get the content of a collection
| Attributes | Values | |||
|---|---|---|---|---|
| HTTP Method | GET | |||
| Request URI | http://<ip address>:<port>/restapi/resource/<collection path>artifact/{ collection path } | |||
| HTTP Request Header | Authorization: Bearer <OAuth { OAuth access token>token } | |||
| Response | Content Description | retrieves the content of the requested collection | Response TypeJSON |
Add a collection
| Attributes | values | |
|---|---|---|
| HTTP Method | PUT | |
| Request URI | http://<ip address>:<port>/restapi/resource/<complete artifact/{ complete path of the collection to be added>added } | |
| HTTP Request Header | Authorization: Bearer <OAuth { OAuth access token>token } | |
| Request Content Type | application/atomcoll+xml | |
| Response | 204 No Content - if Success/ 401 - if failsDescription | It adds the specified collection |
Delete a collection
| Attributes | values |
|---|---|
| HTTP Method | DELETE |
| Request URI | http://<ip address>:<port>/restapi/resource/<collection path>artifact/{ collection path } |
| HTTP Request Header | Authorization: Bearer <OAuth { OAuth access token>token } |
| Response | 204 No Content - if success/ 401 - if fails. |
...
Please note the following points for the above requests.
...
| Description | It deletes the requested collection if exists. |