[JAMES-2808] DeletedMessage serialization & deserialization

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.4.0
• Component/s: deletedMessageVault
• Assignee: Unassigned
• Reporter: Benoit Tellier
• Created: 24/Jun/19 10:11
• Updated: 11/Jul/19 07:26
• Resolved: 11/Jul/19 07:26

Description

BlobStore takes/retrieves InputStream/bytes. We need a component to serialize/deserialize DeletedMessage and related storage information into InputStream and vice versa. (See `DeletedMessageWithStorageInformation` in JAMES-2807 )

Currently, there are two parts of a deleted message:

• Metadata represented by the DTO:

public class DeletedMessage {
    private final MessageId messageId;
    private final List<MailboxId> originMailboxes;
    private final User owner;
    private final ZonedDateTime deliveryDate;
    private final ZonedDateTime deletionDate;
    private final MaybeSender sender;
    private final List<MailAddress> recipients;
    private final Optional<String> subject;
    private final boolean hasAttachment;
    private final long size;

    // storage information
    private final BucketName bucketName;
    private final BlobId blobId;
}

• Content represtented by InputStream

We can consider the Serializer will be in charge of serializing/deserializing just DTOs. And the Vault saves each deleted message into two parts, metadata will be stored in DeletedMessageMetadataVault. and It uses this serializer to serialize DeletedMessage into json and save it as a field in cassandra column