[JAMES-3095] Port to jmap mailboxes/get

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.6.0
• Assignee: Unassigned
• Reporter: René Cordier
• Created: 06/Mar/20 09:28
• Updated: 27/Aug/20 02:26
• Resolved: 06/Jul/20 01:38

Description

After #1662

Constrains for the /get objects in general

• if `ids` is null, return all records. The number of returned elements should not exceed `maxObjectsInGet` (in case James implement `Session Resource`)
• return only requested `ids`
• return all properties by default
• return an empty `list` when not found
• the request `ids` can contains duplicated ids, but server should return a distinct set of Mailbox objects despite of duplicated `ids`.
• don't implement `state` and `sessionState`
• implement `requestTooLarge` in case of too many requested ids - this parts should be connected to JMAP error handling
• Need to validate: Current James doesn't support accountId, should we let it un-validated?

Constrains for mailboxes/get object

• related constrains in properties definition of the documentation
• `totalThreads`: we don't support threads for now (return 1)
• `unreadThreads`: we don't support threads for now (return `unreadEmails` > 0)

Implementation

• Reuse the GetMailboxesRequest and GetMailboxesResponse
• Modify if necessary to match with the new POJO model
• Implement the new MailboxesGetMethod

DOD: full fill all mentioned constrains, unit tests + integration tests