URI
<groupMembers_uri>/{memberid}[.<format>]
Supported methods
Parent resource
Introduction
The groupMember resource is a member of the group. Group member information check is allowed.
Supported Methods:
- GET: Check the member information of the group.
- HEAD: Check whether the groupMember resource exists. or to access the groupMember resource.
Supported output formats: rjson, json, html, xml.
Resource hierarchy
HTTP request methods
Implement the HTTP request on the following URI, where supermapiportal is the server name, with rjson being the output format.
http://supermapiportal:8090/iportal/web/groups/{id}/members/{memberid}.rjson
GET request
Check the member information of the group.
Response structure
When you implement the GET request on the groupMember resource to acquire the specified member information, the structure of the response is as follows:
| Field | Type | Description |
| groupId | Integer | The group id. |
| groupRole | GroupRole | The role of the group member. |
| id | Integer | The id of the group member. |
| joinTime | Long | Time to join the group. |
| memberDescription | String | The descriptive information of the group member. |
| roleUpdateTime | Long | The update time of the group member. |
| userName | String | The group member name. |
Response example
When you implement the GET request on the groupMember resource http://localhost:8090/iportal/web/groups/2/members/12.rjson to acquire the information of the member with id 12 in the group, the rjson format representation of the resource is as follows:
{
"groupId": 2,
"groupRole": "MEMBER",
"id": 12,
"joinTime": 123123243,
"memberDescription": null,
"nickname": "xiaozhao",
"roleUpdateTime": 12423432543,
"userName": "zhaoyuan"
}
HEAD request
Asks for the response identical to the one that would correspond to a GET request, but without the response body. This is useful for retrieving meta-information written in response headers, without having to transport the entire content. The meta-information includes the media-type, content-encoding, transfer-encoding, content-length, etc.
HEAD request can be used to check if the groupMember resource exists, or if the groupMember resource can be accessed by clients. It can also determine if the groupMember resource supports an output format <format> if performed on a URI with .<format> included.