[
https://issues.apache.org/jira/browse/JAMES-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3349.
---------------------------------
Resolution: Fixed
https://github.com/linagora/james-project/pull/3652 solved this
> [JMAP] Method level error handling
> ----------------------------------
>
> Key: JAMES-3349
> URL: https://issues.apache.org/jira/browse/JAMES-3349
> Project: James Server
> Issue Type: Improvement
> Reporter: Nguyễn Việt Đức
> Priority: Major
>
> Once we handle GetMailboxes, we can start managing method level errors.
> *https://jmap.io/spec-core.html#errors*
> {code:java}
> An error response looks like this:
> [ "error", {
> "type": "unknownMethod"
> }, "call-id" ]
> The response name is error, and it MUST have a type property. Other
> properties may be present with further information; these are detailed in the
> error type descriptions where appropriate.
> serverFail: An unexpected or unknown error occurred during the processing of
> the call. A description property should provide more details about the error.
> The method call made no changes to the server’s state. Attempting the same
> operation again is expected to fail again. Contacting the service
> administrator is likely necessary to resolve this problem if it is persistent.
> unknownMethod: The server does not recognise this method name.
> invalidArguments: One of the arguments is of the wrong type or is otherwise
> invalid, or a required argument is missing. A description property MAY be
> present to help debug with an explanation of what the problem was. This is a
> non-localised string, and it is not intended to be shown directly to end
> users.
> accountNotFound: The accountId does not correspond to a valid account. {code}
> See the error registry.
> Handle these errors correctly with `Mailboxes/get`
> *DOD* memory integration tests
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
