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 "Gautier DI FOLCO (JIRA)" <se...@james.apache.org> on 2019/05/20 08:14:00 UTC
[jira] [Commented] (JAMES-2578) MQs should not rely on Serializable
[ https://issues.apache.org/jira/browse/JAMES-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16843764#comment-16843764 ]
Gautier DI FOLCO commented on JAMES-2578:
-----------------------------------------
We previously rely on Java's serialization to store mail attributes which was brittle.
We have introduced a new Mail API which exposes a dedicated type for attributes, giving them the ability to (de)serialize them to Json avoiding a large set of bug classes.
> MQs should not rely on Serializable
> -----------------------------------
>
> Key: JAMES-2578
> URL: https://issues.apache.org/jira/browse/JAMES-2578
> Project: James Server
> Issue Type: Improvement
> Reporter: Gautier DI FOLCO
> Priority: Major
>
> Mail interface allows people to insert any Serializable object as an attribute.
> For now, we then relied on java serialization when putting Mail object into a MQ.
> Now that we try to write a new MailQueue on top of RabbitMQ, it makes sense to try to avoid this use of Serializable.
--
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