[
https://issues.apache.org/jira/browse/JAMES-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
René Cordier closed JAMES-3474.
-------------------------------
Fix Version/s: 3.6.0
Resolution: Done
> Email/set should handle oldState & newState
> -------------------------------------------
>
> Key: JAMES-3474
> URL: https://issues.apache.org/jira/browse/JAMES-3474
> Project: James Server
> Issue Type: Sub-task
> Reporter: Lan Khuat
> Priority: Major
> Fix For: 3.6.0
>
>
> From spec: https://jmap.io/spec-core.html#set (section 5.3)
>
> {code:java}
> oldState: The state string that would have been returned by Foo/get before
> making the requested changes, or null if the server doesn’t know what the
> previous state string was.
> newState: The state string that will now be returned by Foo/get.
> {code}
>
> h1. How
> - When a Email/set request is received, we need to fetch the current state of
> the Email objects. This should be returned as `oldState` property in the
> response.
> - After all the changes in the Mailbox/set request have been applied
> successfully, we should create a new state, store it in the
> EmailChangeRepository and return it with the response as `newState` property.
> - If all the methodCalls in the request end up failing then no new state
> should be generated.
> h1. DoD
> Integration tests to show that the Mailbox/set method can return oldState &
> newState property.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
