This section explains the following REST operations regarding the collection which have been secured with OAuth 2.0.
- Get the content of a collection.
- Add a collection
- Delete a given collection
Table of Contents |
---|
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 | /artifact/{ collection path } |
HTTP Request Header | Authorization: Bearer { OAuth access token } |
Description | retrieves the content of the requested collection |
Add a
...
Collection
Attributes | values |
---|---|
HTTP Method | PUT |
Request URI | /artifact/{ complete path of the collection to be added } |
HTTP Request Header | Authorization: Bearer { OAuth access token } |
Request Content Type | application/atomcoll+xml |
Description | It adds the specified collection |
Delete a
...
Collection
Attributes | values |
---|---|
HTTP Method | DELETE |
Request URI | /artifact/{ collection path } |
HTTP Request Header | Authorization: Bearer { OAuth access token } |
Description | It deletes the requested collection if exists. |
...