You are viewing a plain text version of this content. The canonical link for it is here.

Posted to server-dev@james.apache.org by "Tellier Benoit (JIRA)" <ji...@apache.org> on 2019/05/20 03:45:00 UTC

[jira] [Resolved] (MAILBOX-363) JSON DTO for MessageMove event

     [ https://issues.apache.org/jira/browse/MAILBOX-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tellier Benoit resolved MAILBOX-363.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.3.0

Commits 26af5b2bd46dedc2e7734f508930443566639891 8a91427cd33024aa619f2839ce78b985e5c6b9bd and e151594fda77db2dae2aa5f524e26f6afd367a3e did solve this

> JSON DTO for MessageMove event
> ------------------------------
>
>                 Key: MAILBOX-363
>                 URL: https://issues.apache.org/jira/browse/MAILBOX-363
>             Project: James Mailbox
>          Issue Type: New Feature
>          Components: events
>            Reporter: Tellier Benoit
>            Priority: Major
>             Fix For: 3.3.0
>
>
> Regarding the job dome in MAILBOX-359 define DTO and DTO module for `MessageMove event`.
> You should be able to serialize and deserialize this event in your test. Include JSON loaded from a resource file to demonstrate stability.
> We need to no more link messages in MessageMoveEvents



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org